Closed Bug 144355 Opened 23 years ago Closed 23 years ago

IMAP empty trash on exit preventing app from exiting

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 106479

People

(Reporter: will.sargent, Assigned: Bienvenu)

Details

Attachments

(1 file)

I am running Windows 2000 SP2, 2002051006. I have an IMAP account on a corporate machine that I access through SSH port forwarding. All the ports are the same, so I have mozilla connect the ports to localhost:137. I am using cygwin ssh (which I believe is the OpenSSH project packaged up). Two very bad things can happen to the mail client. 1) If I quit (using ctrl-Q, no quick launch) Mozilla then Mozilla still exists as a background process, and keeps the ports open. I know this because my SSH port forwarding explicitly mentions those ports when I try close it. 2) If the network connection wobbles (i.e. I lose SSH, or I log in using the VPN, which kills the SSH connection) then Mozilla will hang and not return any output. I have to kill it from the task manager before it will go away. I don't know if this will still happen on non SSH clients.
QA Contact: huang → stephend
Ugh, this is happening pretty consistently. Much hanging of browser. The wierd thing is that it seems to block other applications as well when it hangs; I can't start new applications from explorer until I kill Mozilla from the task manager, and then they will all come up at once. Still no clue how this is happening or why Mozilla is keeping three IMAP ports open after I quit it.
Okay, I can get this down to a single test case. Set up an SSH connection as follows: ssh -L 389:ldap.example.com:389 -L 143:imap.example.com:143 -L 25:mail.example.com:25 firewall.example.com Set up an IMAP account on Mozilla. Click "Get New Mail" on Mozilla. Quit Mozilla. Mozilla will still exist as a background application with three IMAP connections open (checking with netstat). Clicking on the Mozilla icon on the desktop will not bring up Mozilla until the existing process is killed.
What's also interesting is that I can replicate this simply by closing the mail client, even if I have other Mozilla Navigator windows open at the time. The other windows will not update the UI and will not respond to right-clicking in the task bar.
Okay, I have a debug RC2 build, and when running through the test case this is what I see: There's a warning about "resetting null namespace" when I download IMAP mail. Then there's an assert when I call "quit-application" saying "requesting removal of non-existant window." but the application is still running. I halted the debugger, and these are the threads that are still up: nsMsgAccountManager::cleanupOnExit at line 1089. This looks very guilty -- it calls accountManager->GetEmptyTrashInProgress and waits. There's a waiting MemoryFlusher thread. There's a waiting TimerThread thread. nsSocketTransportService is polling. nsDNSService is running getMessage. nsThreadPool::GetREquest is waiting. and nsImapProtocol::ImapThreadMainLoop is also waiting, at line 993. I think I have enough information here to mark this as a confirmed bug. I can turn on various logging thingies if it helps. I have absolutely no knowledge of how mailnews works.
try turning off empty trash on exit and let us know if that helps. My guess is that you're right, and that's the problem.
bienvenu is right; turning off empty trash on exit will allow mozilla to close normally. confirming (using old pacbell account) and reducing severity (because there's a workaround).
Severity: critical → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
OK, changing summary. What imap delete model are you using? (in your imap server settings, "when I delete a message"...) and what kind of imap server? an imap protocol log might help: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap thx, - David
Summary: IMAP client keeps sockets open after exiting application → IMAP empty trash on exit preventing app from exiting
I've put in a request to the IS folx regarding the IMAP server. I suspect it's Netscape Mail Server, but I'm not sure. When I delete a message: Mark it as deleted.
Will, you can do something like: telnet servername.domain.tld port, for me: telnet dredd.netscape.com 143 returns: * OK dredd.mcom.com IMAP4 service (Netscape Messaging Server 4.15 Patch 4 (built Dec 7 2000))
my guess is that you don't have a trash folder at all, and thus we can't empty the trash, but we're not detecting the error. Do you have a trash folder?
The IMAP server seems to be Courier IMAP (it's in the log). You are correct that I do not have a Trash folder in my IMAP directory. Should I need one? And how would I mark an IMAP directory as "Trash" anyway?
I'm not saying that you need an IMAP trash folder, but the fact that you don't have one is causing this hang on exit. However, there's no reason to have "empty trash on exit" selected when you don't have a trash folder, so you should just uncheck it. I'll fix it so it doesn't hang, if I can reproduce it.
Assignee: mscott → bienvenu
this is a dup, and has been fixed in the trunk builds (but not rc1/rc2/moz 1.0) *** This bug has been marked as a duplicate of 106479 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: