Closed Bug 95081 Opened 24 years ago Closed 24 years ago

Compose New Message crashes mozilla

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows ME
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 93971

People

(Reporter: wd, Assigned: brendan)

Details

(Keywords: crash)

BuildID: 2001081208 When I go to compose a new message (or reply or forward) Mozilla crashes. Reproducible: Always Steps to Reproduce: 1.Go into MailNews 2.Click "New Message" button 3. Actual Results: Mozilla Crashed Expected Results: no crash It's been this way for a couple of days for me. I do have the fastload pref enabled, if that makes any difference... Talkback IDs from 2 different machines: TB34042891G TB34041553Y
Disabling Fastload fixed this for me -> Brendan
Assignee: sspitzer → brendan
How about a stack backtrace? Anyone else who enables fastload seeing this? jrgm, IIRC, you tried all dialogs and windows. I'm almost ready with a big patch for bug 68045 that adds checksumming and dependency checking. /be
Both stacktraces are identical: nsXULTreeOuterGroupFrame::ReflowFinished [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsXULTreeOuterGroupFrame.cpp, line 1333] PresShell::HandlePostedReflowCallbacks [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 4786] PresShell::ProcessReflowCommands [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5977] ReflowEvent::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5759] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 524] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 1072] KERNEL32.DLL + 0x248f7 (0xbff848f7) 0x00688b5e 0x00058f64
If I keep fastload enabled and I delete XUL.mfl then the New Message window will open fine the first time. But subsequent opens will cause the crash. This problem did not originally occur when fastload was merged into the nightlies. It only started happening near the end of last week I believe.
Keywords: crash
I've been through every dialog, although not a full functional test of each one. It has been a while since I've done that, though. Nevertheless, this is a common crash in recent days, and it is occurring with or without enabling the fastload pref. (Side note: the trunk does have some ugly stuff where it is failing to pull resources out of XUL files. I think we need to get some traction on that before you land these new changes, Brendan. See bug 93558 and kin). *** This bug has been marked as a duplicate of 93971 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.