Closed Bug 280287 Opened 20 years ago Closed 19 years ago

Often shows as still running long after exit.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 246909

People

(Reporter: email, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Thunderbird 1.0 When I exit Thunderbird its windows closes and its indicator disappears from the Windows Status bar. However, when I shut down the PC, sometimes as long as twenty minutes later, I get a message that it's still running. Also, if I check the Windows Task Manager before shutdown, it often shows as a running process long after I've exited. I can shut it down via "End Process". Reproducible: Sometimes Steps to Reproduce: 1. Start Thunderbird 2. Peform functions such as reading and sending Email 3. Exit Thunderbird 4. Wait a few minutes, then look in the Processes tab of the Windows Task Manger window (Ct-Alt-Del) Actual Results: Often it still shows in the Task Manager Processes tab as still running. Expected Results: It should not have still been running.
DUP of Bug 246909? By the way, you say "still running long" but other says "remain", you say "exit" but other says "closing". Searching bug is very very difficult...
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/
I considered posting this in Bug 246909, but this seems to relate more to protocol handling issues. I also have issues with the Thunderbird process not exiting properly, even though the GUI closes. Build Identifier: Thunderbird version 1.6a1 (20051006) Reproducible: Always Steps to Reproduce: 1. Open Thunderbird. 2. (optional) Set Thunderbird to work offline. This eliminates any potential connectivity issues as possible causes. 3. Open a message compose window; for example, by pressing ctrl+n. 4. Close the compose window. 5. Exit Thunderbird. 6. Check the task manager for instances of Thunderbird. Actual Results: Thunderbird is still running, even though the GUI is closed. Further Notes: Even though the process is still running, launching Thunderbird again brings the GUI back to the inbox as it normally does on startup. There is still only one instance of the process, so it appears the process is not frozen. Also, if Thunderbird is configured to ask for offline/online status on startup, launching Thunderbird again if the process has not exited correctly does not request offline/online status as it normally would. Instead, it just returns the GUI directly to the inbox. Could this be related to Bug 311369?
I just tested 1.5b2. The issue I described in Comment #3 does not occur in 1.5b2, nor does Bug 311369. Strange.
*** This bug has been marked as a duplicate of 246909 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.