Interesting choice over there to close the issue so quickly rather than asking for more info, although you didn't give them much to go on.
I wonder what was the resolution of the previous problem that frequently caused this sort of thing? Was the error handling improved such that we might reasonably expect the processing to keep going when it hits something it doesn't like, or was it just a quick fix for the one specific thing that happened to be breaking it at the time? Did that one make it to the github tracker?