Dead Parrots (threads)

[Peter Berghold]

I have a rather busy build flow that invokes other builds sometimes in parallel and other things serially.  What I've been observing is thread on the subordinate jobs dying with an error saying "Build XXX already exists" and interestingly enough those build numbers don't show up in the build history.

I'm running version 1.633 which I just upgraded to two weeks ago. That, by the way, was a flaming disaster causing me to lose all my old job definitions, but that's another story.

SO:  what is causing the threads to die and what do I do about it?   It's becoming ridiculous...