My primary work environment is a laptop using wireless to a ADSL router, and most of the time I'm running a VPN software, that adds a virtual network tunnel to the picture. About 3-4 times a day, either the VPN connection breaks down (stalls), or my ADSL router crashes. When that happens, I usually have the SeaMonkey application (1.0) running, using IMAP+SSL. Very often, at the time the network goes down, Seamonkey stops responding. I finally have compiled an optimized package with debug info, and today I attached to the stalled process with the debugger. I'm attaching the stack trace of all 13 active threads. I confess this version of Seamonkey is not a plain version. For dogfood reasons I've applied the patch from bug 111384, which is a serious change to our SSL networking. But I regularly saw this application hang in versions without my patch, too, so I hope this is unrelated. Maybe you could have a look at the attached stack traces. There are 3 threads doing IMAP I/O, stopped in PR_Lock calls for two different locks.

this is a dup of bug 312775 - since you can reproduce this regularly, Kai, I might have you try some patches if I can come up with any. *** This bug has been marked as a duplicate of 312775 ***

> since you can reproduce this regularly, Kai, I > might have you try some patches if I can come up with any. I'll be glad to try them.