Red Hat Bugzilla – Bug 130966
mozilla segfaults with mail window
Last modified: 2007-11-30 17:10:48 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.7.2) Gecko/20040803 Description of problem: The new version from Fedora Core 2 updates segfaults regularly. It is probably a problem with the mail component of mozilla, as I did not yet see the segfaults when I did not open the Mail window. If I have the mail window open mozilla goes away with segfault after a few minutes. The segfault happens even when I'm currently not in the mail window, so I suspect it could be related to the checking for new mail. Also there was no announcement for this mozilla Version on the fedora-announce-list ? Version-Release number of selected component (if applicable): mozilla-1.7.2-0.2.0 How reproducible: Always Steps to Reproduce: 1. Open mozilla Mail window 2. Wait some minutes 3. Actual Results: segfault Additional info:
Created attachment 103155 [details] A ddd session with a stack backtrace I hope you can use this backtrace, ddd complained about a frozen mouse and tried to continue mozilla, so mozilla already exited after the segfault and so the backtrace could not access the process memory.
Created attachment 103157 [details] Now I got a better stackbacktrace (using directly gdb) I now have a better stack backtrace. This backtrace aids my assumption that the mail part of mozÃlla is the culprit, as the crash happens in nsImapMailFolder::UpdateImapMailboxInfo Sincerly, Klaus
Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match.
Closing per lack of response. Note that FC1 and FC2 are no longer supported even by Fedora Legacy. Please install a still supported version and retest. If this still occurs on FC3 or FC4 and is a security issue, please assign to that version and Fedora Legacy. If it still occurs on FC5 or FC6, please reopen and assign to the correct version.