I don't really think this has anything to do with the original bug or the patch. Nothing in that code would cause the CPU to be tied up. A deadlock would be idle and I'm sure the original bug was manifesting that way, though I never saw it happen. This can't be that bug. -- Scott