533266 - Second MOZ_NO_REMOTE instance crashes when opening mail/news or composer

Status: RESOLVED WORKSFORME

(SeaMonkey :: Startup & Profiles, defect)

Description

[mozbug]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1) Gecko/20090612 Firefox/3.5 Mnenhy/0.7.6.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1) Gecko/20090612 Firefox/3.5 Mnenhy/0.7.6.0

When running a second seamonkey instance with the MOZ_NO_REMOTE=1 variable starting the mail/news or composer component crashes the entire process with no crash reporter and a rather bland error message. There could be some architectural reason this couldn't work but the crash is still annoying.

Reproducible: Always

Steps to Reproduce:
1. Start seamonkey
2. Set the MOZ_NO_REMOTE environmental variable to 1 and start a second seamonkey with its own -p profile
3. Open mail news, or composer or try and subscribe to an RSS feed
Actual Results:  
Crash

Expected Results:  
Something a little more gentle

Comment 1

[lenochod]

What version of SeaMonkey are you using?

I using instead MOZ_NO_REMOTE = 1:

seamonkey.exe -no-remote -P profilename

Comment 2

[mozbug]

win32 Seamonkey 2.0 release build.

Starting with -no-remote -P profilename once apears to have permantly fixed the problem which I reproduced consistently tens of times before filing...

If it wasn`t the code then I suspect during 2.0 migration the flash drive I use for this profile ran out of space leaving the mail part of the profile botched and inducing a consistent crash, or something. There was plenty of space during the crashes before using -no-remote. Maybe I messed up changing TEMP and TMP during the -no-remote run for which I didn`t use my normal batch file which kicked some remaining migration along. Or maybe a recent plugin update kicked in... Sorry to bother you and glad this WORKSevenFORME now.