User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 When I try to close Mozilla, it won't do so. It appears to have closed, but when I check the Task Manager, it still shows up, gobbling up about 44k of my memory. Not a significant loss of memory, no, but it also interferes if I intend to do a uninstall or reinstall of Mozilla, as it won't do so if Mozilla is still active. I've tried ending the process and the process tree in Task Manager numerous times. It still does not work. Reproducible: Always Steps to Reproduce: 1. Open Mozilla 2. Close Mozilla 3. Check Task Manager, or attempt a reinstall or uninstall Actual Results: It refused to exit, uninstall or reinstall. Expected Results: Mozilla should have closed completely.
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.