152527 - crash if starting mozilla -p profile_name with profile on network share

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Walter Haidinger]

BuildID:    2002053012

In order to bypass the profile manager at startup, I've created a Windows
desktop link with the destination 'C:\Programme\Mozilla\mozilla.exe -p
profile_name'.
"profile_name" is an existing, valid profile which can be selected in the
profile manager. However, it is stored _remotely_ on a samba share. While there
is no problem when chosen from the profile manager, the above link chrashes
mozilla with an unhandled exception (I've already submitted a talkbalk report).
Please note that I have not had any problems selecting profiles that way which
are available locally (i.e. skips profile manager and loads ok). Therefore, I
_suspect_ that the crash is related to the profile being remote.


Reproducible: Always
Steps to Reproduce:
1. Create a desktop link and add the -p option 
2. Click in the item to launch mozilla
3.

Actual Results:  Crash: Unhandled Exception.
Talkback manager loads claiming a stack corruption.

Expected Results:  No crash, load of the selected profile without opening the
profile manager.

PS: I've assigned this bug to the "Browser General" component as mozilla
chashes immediately upon start and I simply did not find an appropriate component.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Stack from the talkback for reporter's email address and with the correct
reproduction scenario:

DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1621]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]
DOMGCCallback [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp,
line 1623]

Over to JS engine for a look....

Comment 2

[Johnny Stenback (:jst)]

Soemone would need to test this, but it looks like we end up calling
nsJSEnvironment::Init() twice and the first call most likely fails so we don't
set the static isInitialized to true (and thus we end up setting
gOldJSGCCallback to DOMGCCallback and once the GC callback is called it ends up
calling itself over and over). This could be due to failure to initialize
LiveConnect or failure to access the XPConnect service. Over to DOM since I
doubt this is a JS engine problem.

Hmm, the more I think about this the more I think isInitialized in
nsJSEnvironment::Init() should be set to true even if we fail to get the
XPConnect service or if LiveConnect initialization fails since if either of
those failures occure once, it's very unlikely that an attempt at initializing
nsJSEnvironment will result in anything other than the same failure...

Can someone reproduce this reliably?

Comment 3

[Johnny Stenback (:jst)]

Really reassigning.

Comment 4

[Sivakiran Tummala]

adding the keyword qawanted.

Comment 5

[Michael Lefevre]

reporter (Walter): can you reproduce this bug with a recent build of mozilla
(for example, 1.2.1)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.

Comment 6

[Walter Haidinger]

Tried to reproduce this bug using Mozilla 1.2.1 for Win32 under NT4 (same
OS/config when I initially reported the bug). No crash. :-)
Therefore changing status to WORKSFORME, as requested.