Closed Bug 342510 Opened 18 years ago Closed 18 years ago

Seamonkey crashes when Mail is started if seamonkey has been Quicklaunched

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 341595

People

(Reporter: se014a0001, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060622 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060622 SeaMonkey/1.5a

Whenever seamonkey is started with -turbo, the first attempt to open Mail crashes seamonkey. This happens regardless of whether Mail is selected from the System Tray, the Window Menu in the browser, or from a Mail shortcut. As long as seamonkey was Quicklaunched, it crashes.

Reproducible: Always

Steps to Reproduce:
1."C:\Program Files\mozilla.org\SeaMonkey\seamonkey" -turbo
2. Go to systray, click seamonkey icon, select mail
3. Seamonkey crashes

Actual Results:  
Also fails if you select mail from the Navigator. The common thread is always that seamonkey was started with -turbo

Expected Results:  
Mail window should open

This problem was introduced sometime between the beginning of June, and the 19th.
Are you sure that this wasn't an Duplicate for Bug 341595? 
It would be helpful, if you can provide an Talkback-Crash-ID for the Stack here. 
Bug 341595 was caused by an broken XUL.mfl after first Start of SeaMonkey-Builds later than 20060612. 

Probably you can try to disable the Fastload-File and -caching adding:

// Disable XUL-Caching and XUL.mfl
user_pref("nglayout.debug.disable_xul_cache",     true);
user_pref("nglayout.debug.disable_xul_fastload",  true);

to your user.js or adding the Preferences via about:config. Note, that you have to delete the user_pref from user.js *and* restore the Default-Settings via about:config (Reset) to delete this settings. Setting this Preferences has stopped the Crashes from Bug 341595 almost for me. 
Talkback crash IDs, as requested. TB20185051Y, TB20183379Q, TB20182328K. As to whether this is a duplicate of 341595, how can I tell??? No mention of Quicklaunch there. I will try the suggested user.js settings and report further.
Seems to be the same bug as bug 342332 and probably bug 341595. If this is the case it applies to All operating systems since bug 342332 is in MacOS X.
I have now tried Tobias's user.js settings (see above) and I haven't crashed Seamonkey since. What is the penalty for using these settings? 
(In reply to comment #4)
> I have now tried Tobias's user.js settings (see above) and I haven't crashed
> Seamonkey since. What is the penalty for using these settings? 
> 
Startup was a little slower, and also painting of opend windows (MailNews at Example) I presume. I have got the hint to disable xul-caching from Karsten "mnyromyr" Düsterloh, so the credits go to him. 

And thanks for your TB-IDs, the Stack is looking very similar to the attached in Bug 341595, so I bet this here was an Duplicate. 
If disabling fastload fixes it, then this is bug 341595

*** This bug has been marked as a duplicate of 341595 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Version: unspecified → Trunk
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.