Closed Bug 245513 Opened 21 years ago Closed 20 years ago

Thunderbird leaves uw-imapd processes spinning (possible deadlock?)

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: rschm, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Build Identifier: Thunderbird 0.6 (20040502) I use an XP laptop with Thunderbird 0.6 to access uw-imap on a server (over WLAN). uw-imap is provided by the latest cygwin install (as of June 2nd 2004). This works great, usually a long while (say 1-3 hours). It doesn't seem to matter how many folders I open or mails I read. Suddenly TB stops loading data from the server (UI responds, but throbber throbs, nothing new loads). On the server, I then notice that several uw-imapd processes are running at 100%. Every 10 minutes (new mail poll), a new uw-imapd hangs this way, and my server slowly dies. I can kill all of these processes, and TB starts responding properly again. I've used several other clients with uw-imapd, without problems (Eudora, Outlook, Bynari Insight Connector (to sync all my Outlook data through IMAP)). Reproducible: Always Steps to Reproduce: 1.Configure TB to access (cygwin) uw-imap on server 2.Leave running, use normally (occasionally read mails, open folders, ...) Actual Results: TB fails to load any data from uw-imap. An increasing number of uw-imapd processes choke the server (one seems to be added for every access). Expected Results: TB should have been able to work with uw-imap indefinitely.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.