User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016 Periodically Mozilla has simply terminated. I haven't marked this higher priority due to frequency and the impact seems to limited to a restart (no data loss). In all cases I was not using Mozilla mail or the browser actively. Focus was on other applications. However, browser windows have been open and mail has been checking for and downloading new mail from several POP accounts. It appears to happen when making POP requests. I don't have as much data as I'd like to on this. This is as much for tracking as anything. I'll post updates if I can get something more solid. Unfortunately I have't got any ideas on how to reproduce this yet. Suggestions on collecting more useful data would be appreciated. Can someone point me to where/how I can get more detailed trace info? I'm running the Moz 1.5 rpm behind a firewall device. I have looked at couple of nspr log files, unfortunately only I have only one at this time. The last entries showed mozilla talking to my POP server. In the good log, the last line shows "POP3: Entering state: 25" at the time it failed. No evidence of core file or other footprint of the problem. (I also have netstat data and every time "SEND: USER" is logged. Now I'm adding data from ps on mozilla-bin) It *might* be related to http://bugzilla.mozilla.org/show_bug.cgi?id=165832 . The nspr log shows that mozilla stopped talking to one of my three POP accounts (but this was 7 hours before the crash). I reviewed a large number of bugs with terminated | unexpectedly | dies | crash+linux | crash+backgroup before posting. There were too many under crash | crash+mail to comprehensively review. I also revied the 1.6b changelog. No entires seemed to fit. Thanks, David Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: Not crashed.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.