User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090714 Shredder/3.0b3pre About half the time, when I come home at night, Thunderbird is still running in the Task Manager, even though I thought I had closed (exited) the program in the morning. My theory is that when there is a pop-up about a new version to install, and I don't install or update, that the Thunderbird process never exits, even after you exit the program. Reproducible: Always Steps to Reproduce: 1. Start Thunderbird 2. Wait for pop-up about new version 3. Close Thunderbird Actual Results: Watch Task Manager, thunderbird.exe process never exits Expected Results: thunderbird.exe process should eventually exit

Using gmail via IMAP Deleted mail moved to [gmail] Trash folder Sent mail moved to [gmail] Sent folder

When this happens what do you see if you pass a netstat -an ? Wayne anything else that I should ask ?

Jim, can you test your theory about the update? i.e. turn off updates? (although, I doubt this is the issue) ludo, I normally also ask whether cpu is high or zero

Yes, the Thunderbird process is consuming a whole CPU while it's running (and the application is "closed"). Here's the output of netstat (the LAN is 10.10.220.*): Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:13 0.0.0.0:0 LISTENING TCP 0.0.0.0:25 0.0.0.0:0 LISTENING TCP 0.0.0.0:37 0.0.0.0:0 LISTENING TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:443 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:1036 0.0.0.0:0 LISTENING TCP 0.0.0.0:2002 0.0.0.0:0 LISTENING TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING TCP 0.0.0.0:6000 0.0.0.0:0 LISTENING TCP 0.0.0.0:7015 0.0.0.0:0 LISTENING TCP 0.0.0.0:7300 0.0.0.0:0 LISTENING TCP 0.0.0.0:14482 0.0.0.0:0 LISTENING TCP 0.0.0.0:31038 0.0.0.0:0 LISTENING TCP 10.10.220.120:139 0.0.0.0:0 LISTENING TCP 10.10.220.120:139 10.10.220.147:2202 ESTABLISHED TCP 10.10.220.120:1032 216.52.233.213:443 ESTABLISHED TCP 10.10.220.120:1394 198.20.8.241:443 CLOSE_WAIT TCP 10.10.220.120:1395 198.20.8.241:443 CLOSE_WAIT TCP 10.10.220.120:1499 204.2.160.25:80 CLOSE_WAIT TCP 10.10.220.120:1651 204.2.160.59:80 CLOSE_WAIT TCP 10.10.220.120:1652 204.2.160.59:80 CLOSE_WAIT TCP 10.10.220.120:1657 204.2.160.233:80 CLOSE_WAIT TCP 10.10.220.120:1658 204.2.160.24:80 CLOSE_WAIT TCP 10.10.220.120:1671 204.2.160.49:80 CLOSE_WAIT TCP 10.10.220.120:1674 204.2.160.49:80 CLOSE_WAIT TCP 10.10.220.120:1677 128.241.220.80:80 CLOSE_WAIT TCP 10.10.220.120:1680 128.241.220.80:80 CLOSE_WAIT TCP 10.10.220.120:1681 204.2.160.26:80 CLOSE_WAIT TCP 10.10.220.120:1682 216.137.37.216:80 CLOSE_WAIT TCP 10.10.220.120:1683 216.137.37.216:80 CLOSE_WAIT TCP 10.10.220.120:1684 64.236.76.160:80 CLOSE_WAIT TCP 10.10.220.120:1692 204.2.160.19:80 CLOSE_WAIT TCP 10.10.220.120:1693 204.2.160.19:80 CLOSE_WAIT TCP 10.10.220.120:1759 209.85.225.118:80 CLOSE_WAIT TCP 10.10.220.120:1988 198.20.8.241:443 CLOSE_WAIT TCP 10.10.220.120:1989 198.20.8.241:443 CLOSE_WAIT TCP 10.10.220.120:2182 38.97.103.142:443 ESTABLISHED TCP 10.10.220.120:2380 209.85.225.118:80 ESTABLISHED TCP 10.10.220.120:2420 208.67.219.231:443 ESTABLISHED TCP 10.10.220.120:2422 199.7.71.72:80 TIME_WAIT TCP 10.10.220.120:2423 216.252.124.207:80 TIME_WAIT TCP 10.10.220.120:2425 74.125.19.83:443 ESTABLISHED TCP 10.10.220.120:2426 199.7.71.72:80 TIME_WAIT TCP 10.10.220.120:2428 74.125.19.83:80 ESTABLISHED TCP 10.10.220.120:2429 208.67.219.231:80 ESTABLISHED TCP 10.10.220.120:2430 74.125.19.83:80 ESTABLISHED TCP 10.10.220.120:2433 74.125.19.132:80 ESTABLISHED TCP 10.10.220.120:2434 74.125.19.83:80 ESTABLISHED TCP 10.10.220.120:2435 74.125.95.189:80 ESTABLISHED TCP 10.10.220.120:2444 74.125.95.100:80 ESTABLISHED TCP 10.10.220.120:2449 63.245.209.58:80 TIME_WAIT TCP 10.10.220.120:2456 63.245.209.72:443 ESTABLISHED TCP 10.10.220.120:2458 63.245.209.72:443 ESTABLISHED TCP 10.10.220.120:2460 63.245.209.72:443 ESTABLISHED TCP 10.10.220.120:2461 63.245.209.72:443 ESTABLISHED TCP 10.10.220.120:2462 63.245.209.72:443 ESTABLISHED TCP 10.10.220.120:2463 63.245.209.11:443 TIME_WAIT TCP 10.10.220.120:2464 63.245.209.11:443 TIME_WAIT TCP 10.10.220.120:2465 74.125.95.121:80 ESTABLISHED TCP 10.10.220.120:2466 64.191.203.30:80 ESTABLISHED TCP 10.10.220.120:2467 74.125.95.121:80 ESTABLISHED TCP 10.10.220.120:2468 209.191.70.46:80 CLOSE_WAIT TCP 10.10.220.120:2865 198.20.8.246:80 CLOSE_WAIT TCP 10.10.220.120:3563 129.21.160.66:5222 ESTABLISHED TCP 10.10.220.120:3732 67.40.148.194:23 ESTABLISHED TCP 10.10.220.120:7300 10.10.220.147:1063 ESTABLISHED TCP 127.0.0.1:668 0.0.0.0:0 LISTENING TCP 127.0.0.1:668 127.0.0.1:1067 ESTABLISHED TCP 127.0.0.1:1039 0.0.0.0:0 LISTENING TCP 127.0.0.1:1052 127.0.0.1:2002 ESTABLISHED TCP 127.0.0.1:1067 127.0.0.1:668 ESTABLISHED TCP 127.0.0.1:1068 127.0.0.1:31416 ESTABLISHED TCP 127.0.0.1:1095 0.0.0.0:0 LISTENING TCP 127.0.0.1:1097 127.0.0.1:6000 ESTABLISHED TCP 127.0.0.1:1098 127.0.0.1:6000 ESTABLISHED TCP 127.0.0.1:1099 127.0.0.1:6000 ESTABLISHED TCP 127.0.0.1:1488 127.0.0.1:27015 ESTABLISHED TCP 127.0.0.1:2002 127.0.0.1:1052 ESTABLISHED TCP 127.0.0.1:2123 127.0.0.1:2124 ESTABLISHED TCP 127.0.0.1:2124 127.0.0.1:2123 ESTABLISHED TCP 127.0.0.1:2125 127.0.0.1:2126 ESTABLISHED TCP 127.0.0.1:2126 127.0.0.1:2125 ESTABLISHED TCP 127.0.0.1:2410 127.0.0.1:2411 ESTABLISHED TCP 127.0.0.1:2411 127.0.0.1:2410 ESTABLISHED TCP 127.0.0.1:2414 127.0.0.1:2415 ESTABLISHED TCP 127.0.0.1:2415 127.0.0.1:2414 ESTABLISHED TCP 127.0.0.1:2417 127.0.0.1:5152 FIN_WAIT_2 TCP 127.0.0.1:4675 127.0.0.1:7300 ESTABLISHED TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING TCP 127.0.0.1:5152 127.0.0.1:2417 CLOSE_WAIT TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING TCP 127.0.0.1:6000 127.0.0.1:1097 ESTABLISHED TCP 127.0.0.1:6000 127.0.0.1:1098 ESTABLISHED TCP 127.0.0.1:6000 127.0.0.1:1099 ESTABLISHED TCP 127.0.0.1:7300 127.0.0.1:4675 ESTABLISHED TCP 127.0.0.1:8791 0.0.0.0:0 LISTENING TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING TCP 127.0.0.1:27015 127.0.0.1:1488 ESTABLISHED TCP 127.0.0.1:31416 0.0.0.0:0 LISTENING TCP 127.0.0.1:31416 127.0.0.1:1068 ESTABLISHED TCP 127.0.0.1:62514 0.0.0.0:0 LISTENING UDP 0.0.0.0:13 *:* UDP 0.0.0.0:37 *:* UDP 0.0.0.0:123 *:* UDP 0.0.0.0:445 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:1025 *:* UDP 0.0.0.0:1030 *:* UDP 0.0.0.0:3068 *:* UDP 0.0.0.0:3069 *:* UDP 0.0.0.0:3456 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:58860 *:* UDP 10.10.220.120:137 *:* UDP 10.10.220.120:138 *:* UDP 10.10.220.120:1900 *:* UDP 10.10.220.120:5353 *:* UDP 127.0.0.1:1377 *:* UDP 127.0.0.1:1646 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:2197 *:* UDP 127.0.0.1:2395 *:* UDP 127.0.0.1:62514 *:*

I should have added, updates have been turned off for 2 days. This is the first instance since then of the process not exiting.

I have the same happening on both Win 2K and XP. Thunderbird 3b3 with lightning 1b Love it basically. I exit, and the process never releases. I need to go to Task manger to kill the process before TB can be opened. When TB running, no CPU time. here is netstat -an for three modes. Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:7 0.0.0.0:0 LISTENING TCP 0.0.0.0:9 0.0.0.0:0 LISTENING TCP 0.0.0.0:13 0.0.0.0:0 LISTENING TCP 0.0.0.0:17 0.0.0.0:0 LISTENING TCP 0.0.0.0:19 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:6877 0.0.0.0:0 LISTENING TCP 127.0.0.1:1028 0.0.0.0:0 LISTENING TCP 127.0.0.1:1039 0.0.0.0:0 LISTENING TCP 127.0.0.1:1608 127.0.0.1:1609 ESTABLISHED TCP 127.0.0.1:1609 127.0.0.1:1608 ESTABLISHED TCP 127.0.0.1:1612 127.0.0.1:1614 ESTABLISHED TCP 127.0.0.1:1614 127.0.0.1:1612 ESTABLISHED TCP 127.0.0.1:2074 127.0.0.1:2075 ESTABLISHED TCP 127.0.0.1:2075 127.0.0.1:2074 ESTABLISHED TCP 127.0.0.1:2076 127.0.0.1:2077 ESTABLISHED TCP 127.0.0.1:2077 127.0.0.1:2076 ESTABLISHED TCP 127.0.0.1:2084 127.0.0.1:10299 TIME_WAIT TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING TCP 127.0.0.1:5152 127.0.0.1:1718 CLOSE_WAIT TCP 127.0.0.1:10299 0.0.0.0:0 LISTENING TCP 127.0.0.1:10299 127.0.0.1:2080 TIME_WAIT TCP 127.0.0.1:10300 0.0.0.0:0 LISTENING TCP 127.0.0.1:10301 0.0.0.0:0 LISTENING TCP 127.0.0.1:10302 0.0.0.0:0 LISTENING TCP 127.0.0.1:10303 0.0.0.0:0 LISTENING TCP 192.168.2.10:2078 64.233.169.147:443 ESTABLISHED TCP 192.168.2.10:2082 142.76.1.55:993 ESTABLISHED TCP 192.168.2.10:2086 142.76.1.55:993 ESTABLISHED UDP 0.0.0.0:7 *:* UDP 0.0.0.0:9 *:* UDP 0.0.0.0:13 *:* UDP 0.0.0.0:17 *:* UDP 0.0.0.0:19 *:* UDP 0.0.0.0:445 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:4500 *:* UDP 127.0.0.1:123 *:* UDP 127.0.0.1:1029 *:* UDP 127.0.0.1:1030 *:* UDP 127.0.0.1:1900 *:* UDP 192.168.2.10:123 *:* UDP 192.168.2.10:520 *:* UDP 192.168.2.10:1900 *:* After exit, Mem usage no change - 125Meg and 95% Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:7 0.0.0.0:0 LISTENING TCP 0.0.0.0:9 0.0.0.0:0 LISTENING TCP 0.0.0.0:13 0.0.0.0:0 LISTENING TCP 0.0.0.0:17 0.0.0.0:0 LISTENING TCP 0.0.0.0:19 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:6877 0.0.0.0:0 LISTENING TCP 127.0.0.1:1028 0.0.0.0:0 LISTENING TCP 127.0.0.1:1039 0.0.0.0:0 LISTENING TCP 127.0.0.1:1608 127.0.0.1:1609 ESTABLISHED TCP 127.0.0.1:1609 127.0.0.1:1608 ESTABLISHED TCP 127.0.0.1:1612 127.0.0.1:1614 ESTABLISHED TCP 127.0.0.1:1614 127.0.0.1:1612 ESTABLISHED TCP 127.0.0.1:2074 127.0.0.1:2075 ESTABLISHED TCP 127.0.0.1:2075 127.0.0.1:2074 ESTABLISHED TCP 127.0.0.1:2076 127.0.0.1:2077 ESTABLISHED TCP 127.0.0.1:2077 127.0.0.1:2076 ESTABLISHED TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING TCP 127.0.0.1:5152 127.0.0.1:1718 CLOSE_WAIT TCP 127.0.0.1:10299 0.0.0.0:0 LISTENING TCP 127.0.0.1:10300 0.0.0.0:0 LISTENING TCP 127.0.0.1:10301 0.0.0.0:0 LISTENING TCP 127.0.0.1:10302 0.0.0.0:0 LISTENING TCP 127.0.0.1:10303 0.0.0.0:0 LISTENING TCP 192.168.2.10:2078 64.233.169.147:443 ESTABLISHED UDP 0.0.0.0:7 *:* UDP 0.0.0.0:9 *:* UDP 0.0.0.0:13 *:* UDP 0.0.0.0:17 *:* UDP 0.0.0.0:19 *:* UDP 0.0.0.0:445 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:4500 *:* UDP 127.0.0.1:123 *:* UDP 127.0.0.1:1029 *:* UDP 127.0.0.1:1030 *:* UDP 127.0.0.1:1900 *:* UDP 192.168.2.10:123 *:* UDP 192.168.2.10:520 *:* UDP 192.168.2.10:1900 *:* TB not running: Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:7 0.0.0.0:0 LISTENING TCP 0.0.0.0:9 0.0.0.0:0 LISTENING TCP 0.0.0.0:13 0.0.0.0:0 LISTENING TCP 0.0.0.0:17 0.0.0.0:0 LISTENING TCP 0.0.0.0:19 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:6877 0.0.0.0:0 LISTENING TCP 127.0.0.1:1028 0.0.0.0:0 LISTENING TCP 127.0.0.1:1039 0.0.0.0:0 LISTENING TCP 127.0.0.1:1608 127.0.0.1:1609 ESTABLISHED TCP 127.0.0.1:1609 127.0.0.1:1608 ESTABLISHED TCP 127.0.0.1:1612 127.0.0.1:1614 ESTABLISHED TCP 127.0.0.1:1614 127.0.0.1:1612 ESTABLISHED TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING TCP 127.0.0.1:5152 127.0.0.1:1718 CLOSE_WAIT TCP 127.0.0.1:10299 0.0.0.0:0 LISTENING TCP 127.0.0.1:10300 0.0.0.0:0 LISTENING TCP 127.0.0.1:10301 0.0.0.0:0 LISTENING TCP 127.0.0.1:10302 0.0.0.0:0 LISTENING TCP 127.0.0.1:10303 0.0.0.0:0 LISTENING UDP 0.0.0.0:7 *:* UDP 0.0.0.0:9 *:* UDP 0.0.0.0:13 *:* UDP 0.0.0.0:17 *:* UDP 0.0.0.0:19 *:* UDP 0.0.0.0:445 *:* UDP 0.0.0.0:500 *:* UDP 0.0.0.0:4500 *:* UDP 127.0.0.1:123 *:* UDP 127.0.0.1:1029 *:* UDP 127.0.0.1:1030 *:* UDP 127.0.0.1:1900 *:* UDP 192.168.2.10:123 *:* UDP 192.168.2.10:520 *:* UDP 192.168.2.10:1900 *:*

(In reply to comment #6) > I have the same happening on both Win 2K and XP. > Thunderbird 3b3 with lightning 1b Are you using imap too ? > TCP 192.168.2.10:2078 64.233.169.147:443 ESTABLISHED Hello google. Probably your web browser is running in the background right ? > TCP 192.168.2.10:2082 142.76.1.55:993 ESTABLISHED > TCP 192.168.2.10:2086 142.76.1.55:993 ESTABLISHED Sunnybrook and Women's College Health Sciences Centre. Is this your ISP ?

I am using IMAP, the server is 142.76.something and I am coming in from outside. 142.76.1.55 must be the firewall.

Has something changed? The last couple of releases seem to terminate the thunderbird.exe process immediately. I'm still using GMAIL IMAP. I'm currently running this version: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090907 Shredder/3.0b4pre

Could have been fixed by bug 497059 which is another shutdown related issue...

Tried in the last Thunderbird, still did it. Loaded Shredder 3.0b4pre and it still happens. I have 1 imap link and 2 gmail links and 1 pop. CPU time of the orphan process is 85-95%. There is no network activity showing. With no thunderbird, Idle is above 95%. When Shredder is open, uses over 200K memory, and blocks of time at 99%, but other times it is below 15% I prefer to NOT keep messages on local computer, so turn off synchronization with imap servers. Actually, I think that that might have solved the problem. Nightly downloads must reset the preferences because when I reset to not download all files, TB shut down. Tried 3 times, and no problem. If this is true, please don't default downloads. My email box has 8 years of messages, and has confidential information which MUST not be left on my home machine or laptop. This is a legal requirement for any working in a medical area. Gord

To Jim Reisert(bug opener) and Gord Mawdsley(Comment #11): Will "disable of IDLE command" reduce frequency of your problem? - Server Settings/Advanced, uncheck "[ ] Use IDLE command ..." - If automatic new mail check is needed, enable "Check for new messages every N minutes" option. - Turn on "synchronization with IMAP servers" again for checking. (In reply to comment #11) > please don't default downloads. See already WONTFIX'ed Bug 505759.

RE: Will "disable of IDLE command" reduce frequency of your problem? As I said, the problem seems to have gone away for me. If it comes back, I'll revisit this issue.

I tried the IDLE disable and it worked a few times. The last time it took over a minute to hangup, but the process finally closed on its own. Gebnerated a crash report.

(In reply to comment #14) > Gebnerated a crash report. If Crash Report of Tb is available, open separate bug for crash with Crash Reporter ID. (In reply to comment #13 and comment #14) - After disable auto-sync, prodlem didn't occur. - "Disable of IDLE command reduced frequency slightly. Termination while Tb communicating with server(fetch of mail data)? Other question. Do you terminate Tb by (a) File/Exit (Ctrl+Q)? Or (b) X button at top/right of window or File/Close(Ctrl+W)? If (a), Bug 480466 may be main culprit. It interferes normal shutdown process. (first shutdown process is killed by second shutdown process) If (b), Bug 403837 and Bug 459376 may be relevant. It doesn't invoke normal shutdown process.

Gary, Gordy, reporter's issue is WFM. If you still see a problem, use shutdown hang query at https://wiki.mozilla.org/Thunderbird:Bug_Queries#More_Queries to pick a bug that matches your symptoms => WFM