Closed Bug 195414 Opened 22 years ago Closed 20 years ago

Reading certain mail causes crash

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mozilla, Assigned: sspitzer)

References

Details

(Keywords: crash)

Attachments

(3 files)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.3b) Gecko/20030211 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.3b) Gecko/20030211 This only happens with one particular message, which is devoid of any attachements & containsno HTML! I am going to attach the backtrace I get when trying to read it. Reproducible: Always Steps to Reproduce: 1. Fire up MailNews 2. Click on this email in the list of messages. Actual Results: Mozilla crashes. Expected Results: It should display the message.
Do you use a XFT build ?
Yes, a GTK2 one to be specific.
Keywords: crash
Blocks: xft_tracking
Can you run this with --sync and re-get the stack trace?
Blocks: gtk2
No longer blocks: xft_tracking
This one was produced using 1.3 final release.
Attached file Stacktrace with --sync
Alright, I ran it with --sync & produced yet another stack trace. Hope this one is more useful.
OK, this is very strange. This has suddenly & inexplicably stopped being a problem! All I can think of that I changed was to add a 2nd Usenet account (& subscribe to 2 groups) and change the Inbox folder properties to use UTF-8 by default but to stop overriding the charset specified by the message. After that the message that have been crashing Moz no longer crash it & display just fine. Suspecting that maybe the change to the charset preferences was what did the trick, I set those back to the way they were, restarted Moz & read a few of the problme messages but they still do not cause a problem. Since I cannot see any reason why adding a new News account should have had any effect whatsoever on this situation, I am not going to undo that because I really don't want to reconfigure it.
-->resolving so (since there is also no possibility to reproduce it anymore)...
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: