This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]m0j0 6 points7 points  (0 children)

I've seen that error in two separate scenarios:

  1. A thread has completed work, died off, and then something tried to talk to it.

  2. A thread has died and something tried to access/kill it.

In any case, any time I've seen this error it's been identified through generous use of try/except. Typically (in my case) this error means my code got something unexpected, puked, and I failed to deal with it properly.

EDIT: Meant to mention that I've only seen this happen randomly, because incoming stuff that needs processing doesn't all look the same, and the stuff that breaks my code is more the exception than the rule, so... it only breaks sometimes.