191872 - Cannot start Mozilla with new profile

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Dhruva Reddy]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 MultiZilla/v1.1.22
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 MultiZilla/v1.1.22

I tried to create a new profile (in the course of reporting on bug #191382). 
Mozilla will now not start under this new profile, although I have no trouble
starting under the default profile.

Reproducible: Always

Steps to Reproduce:
1.  Bring up profile manager from the command line (mozilla -profilemanager).
2.  Follow steps to create profile, specifying profile name (as opposed to
accepting the default name).
3.  Exit profile manager.
4.  Start Mozilla.
5.  Select new profile when prompted.
Actual Results:  
The profile manager exits, whether I start from the desktop or the command line
(no error message in the latter case).  The browser window does not come up.  

Expected Results:  
I would have expected the browser window to come up with my new profile.

I do not see any related processes after this happens (ps -fu $LOGNAME | grep
mozilla).

Comment 1

[R.K.Aa.]

i wonder if multizilla is breaking your profile. Can you try uninstall it?

Comment 2

[earthsound]

Mozilla 1.3b, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b)
Gecko/20030210; Windows XP, SP1

Marking as confirmed, as I see this in XP & I do not have multizilla installed.
Someone should mark this OS:All, as I do not have that power. ;)

I don't think I've ever noticed this w/ any build prior to 1.3b

Steps I took:

1) Bring up Profile Manager (mozilla.exe -ProfileManager)
2) Add new profile, named it "new testing profile" (w/o the quotes)
3) Highlighted the new profile I created
4) Clicked start mozilla

Results: 

Nothing happened, aside from Quicklaunch icon getting set in taskbar. As I
hovered my mouse over the Quicklaunch icon, the icon disappeared. Subsequent
attempts showed, via Task Manager, that as soon as I click Start Mozilla, the
process disappears in Applications running list, but the Quicklaunch icon
remains until I hover over it.

Also, if I just run mozilla w/o the -ProfileManager option, I am prompted to
pick a profile. If I pick the newly created one, the results are the same as I
get for the first steps I outlined: i.e., nothing but a non-functional
Quicklaunch icon in the taskbar.

Comment 3

[earthsound]

In subsequent tests, I have managed to only get different results once. Every
other time I created a new profile, mozilla would not launch, but would just
place a Quicklaunch icon in the taskbar which would quickly disappear should I
even hover over it.

However, in the one exception to the rule, I created a new profile and clicked
"Start Mozilla" & the Quicklaunch icon appeared (no new window, though) and did
NOT disappear. However, right clicking on the icon and selecting Navigator did
not bring up a window. Right-clicking and selecting either Mail..., Composer or
Address... resulted in the correct window getting launched. When I opened Mail
from this Quicklaunch, I was unable to open a new window w/ either Ctrl+N or
going to File>New>Navigator Window. I could only open the new window by right
clicking on a URL in the default message waiting in my new profile's inbox and
selecting open in new window.

I have yet to reproduce this exception...

Also, should we remove multizilla from the summary, as I do not have multizilla.

Comment 4

[earthsound]

Maybe this should be changed to critical(?), as a mozilla that won't open is not
good. I managed to do a Dependency Walker (http://www.dependencywalker.com/)
profile of mozilla after I create a new profile. See next 2 attachments. First
one is a zipped text file of the profiling, with timp stamps for each line of
the log. The 2nd is the dwi (dependency walker image file) for those developers
who utilize dependency walker. (Of course, the first one is much lighter)
Everything after the timestamp of 00:00:19.032 shows what happened as I paused
when the Profile Manager came up and then clicked Start Mozilla (under the new
profile).

Comment 5

[earthsound]

Attachment: zipped text file of dependency walker profile of mozilla closing after selecting newly created profile to launch mozilla under

Comment 6

[earthsound]

zipped dwi was too large. You may see it here:

http://phish.marko.net/new/dwi%20profile%20of%20mozilla.zip

Comment 7

[earthsound]

Mozilla 1.3, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3)
Gecko/20030312, Windows XP, Build 2600.xpsp1.020828-1920

I uninstalled 1.3b, installed final 1.3 and created a new profile. Upon
selecting the newly created profile, mozilla just exits. Selecting the default
profile results in what is expected: launching of mozilla. 

I will attach a profile of what happens. It follows the launching of mozilla,
the profile manager popping up and the selection of the new profile to launch
and the closing of mozilla.

Should this not be moved up to major, at least? 

Comment 8

[earthsound]

Attachment: zip of profile showing what happens as mozilla starts/closes on new profile

Notes:

At around 30 seconds into the profile (it is time-stamped) the profile manager
popped up. Everything after that is what happens after I select the newly
created profile and watch in dismay as mozilla just closes, leaving the
quicklaunch icon in the taskbar...it doesn't crash, but obviously the
quicklaunch is dead @ that point. :\

Comment 9

[earthsound]

Mozilla 1.4a, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a)
Gecko/20030401, Windows XP build 2600.xpsp1.020828-1920

still unable to open mozilla w/ a newly created profile :(

Comment 10

[earthsound]

Lots of new info about this. I decided that since I couldn't open mozilla w/ a
new profile using the profile manager I would try to switch profiles while
running mozilla. 

I clicked Tools>Switch Profile. 
Since I only had one profile, I was stepped through the process of creating one.
It was created successfully. 
I selected the newly-created profile and was greeted w/ an alert box. It read:

"Could not initialize the browser's security component. The most likely cause is
problems with files in your browser's profile directory. Please check that this
directory has no read/write restrictions and your hard disk is not full or close
to full. It is recommended that you exit the browser and fix the problem. If you
continue to use this browser session, you might see incorrect browser behaviour
when accessing security features.  
[OK]"

I clicked OK. It then gave another alert (titled Quick Launch):

"Quick Launc is active, so Mozilla remains in memory and can be started again
quickly. To completely exit, click on the Mozilla icon in the system tray and
select Exit Mozilla.
[]Don't show me this message again
[OK]"

I clicked OK. It then shut down Quick Launch and restarted it. This is the point
that mozilla usually crashed (w/o Talkback kicking in) when I try to use a new
profile by using the profile manager. 

Instead of a browser window opening, the Quick Launch icon was the only visible
indication that mozilla was running. I tried clicking/double-clicking the QL
icon, and the profile manager comes up. I select the new profile, but no browser
opens, however, the QL icon remains and mozilla doesn't crash. 

Right-clicking and selecting Navigator results in nothing. Mail/News, Composer &
Address Book all open from Quick Launch. I open a Mail/News window. Ctrl+1 &
Ctrl+N do not open a new window, instead both combos result in this error in the
JavaScript Console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsICmdLineHandler.defaultArgs]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://communicator/content/tasksOverlay.js :: OpenBrowserWindow :: line 108"
 data: no]

Although I cannot open the browser w/ above combos, clicking the Release Notes
link in the mail/news welcome message does bring up a browser window. However, I
soon realize that I cannot open tabs by Ctrl+T or w/ the Open a New Tab button
in the tab toolbar. Both Ctrl+T and the New Tab button result in the following
Javascript Console error:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsICmdLineHandler.defaultArgs]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://navigator/content/navigator.js :: BrowserOpenTab :: line 1029"  data: no]

Any ideas what causes this or any quick/dirty fix available? ;)

Comment 11

[earthsound]

Since successfully enabling a switch to the newly created profile via
Tools>Switch Profile..., subsequent attempts have resulted in Talkback (finally):

TB18894940Y
TB18894707G

Comment 12

[earthsound]

Attachment: Dr. Watson log of the crash

Comment 13

[earthsound]

Attachment: 2nd Dr. Watson log of crash

Comment 14

[earthsound]

Attachment: zipped text file of Dependency Walker profile of crash

compare to 1.3x Dependency Walker profile...

Comment 15

[earthsound]

Mozilla 1.4a, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a)
Gecko/20030401, Windows XP Professional, build 2600.xpsp1.020828-1920

add TB IDs TB19019381K & TB19019404K

Comment 16

[earthsound]

add TB IDs TB19019531K, TB19019552Z, TB19019689Z, TB19019707Z, TB19019722Y,
TB19019738M

Comment 17

[earthsound]

sorry for the spam, but this should be marked critical

Comment 18

[Boris Zbarsky [:bzbarsky]]

stephend, could you get some of those stacks?

Comment 19

[HJ]

Changing OS to all (see command #2) and removing [multizilla] because this is
not MultiZilla related.

Comment 20

[HJ]

Huh? I got some strange error about .net accounts exceeding the maximum level of
100. Is that why this [e-mail] was also added, or was this just an
coincidental event?

Comment 21

[earthsound]

this bug should be marked WFM. I haven't reproduced it in >3 years, and nothing has been added to this >2 years.

Comment 22

[Philip Chee]

> this bug should be marked WFM.
Done.