Date: 25/5/2004
From the feedback I've been getting it appears that the 100% CPU hang in Scribe has indeed been fixed in the most recent test build. On top of that the other major showstopper: not being able to reliably send to multiple recipients bug also has a possible fix in place. So all in all I'm feeling like I'm getting on top of the bug situation with Scribe and my todo list has a whole lot less critical things on it now than for most of the year.

The hang bug was caused by a incorrect error code returned by windows. Which confused the threading code such that the thread would start executing but the owning object would think that it had failed to start. So you can imagine the sort of confusion that would ensue. I'm learning not to trust the windows error codes the hard way. It seems obvious in hindsight, but everything always is.

Email (optional): (Will be HTML encoded to evade harvesting)
Remember username and/or email in a cookie.
Notify me of new posts in this thread via email.