26102 - [PP]Cannot launch second time.

Status: VERIFIED FIXED

(SeaMonkey :: Build Config, defect, P1)

Description

[Grace Bush]

Steps to reproduce:
1. download mozilla...bin file, clean mozregistry and profiles folder
2. choose Mozilla ProfileManager or Mozilla ProfileWizard
3. Fill in data and press start
4. Seamonkey is launched- 
5. Quit seamonkey
6. Choose Mozilla Select Profile or another option

Actual results: crash on exit (will get stack crawl after testing netscape...bin 
file- 2nd launch shows splash screen then stops

Expected results: no crash, relaunch 

build 2000020109

Comment 1

[Daniel (Leaf) Nunes]

checking with developers to see if this is, in fact, a packaging/build problem.
My suspicion is that it is not.

Also, did you see this behaviour with the mac mozilla-only build?

Comment 2

[Grace Bush]

tested with commercial build- which does not crash on exit but hangs 
necessitating a reboot. Second launch not possible here either

Comment 3

[Doug Turner (:dougt)]

grace, What happens when you delete the file named "Components Registry" 
which live next to the mozilla executable?  Does this allow you to launch 
more than twice.  If so, please attach your origanal components registry file 
to the bug report.

Comment 4

[Mike Pinkerton (not reading bugmail)]

if this is holding the tree closed, how about some traction on that stack trace? 

It works for 3 of us in mozilla (non-commercial) debug builds.

Comment 5

[Grace Bush]

Attachment: component registry from first launch, netscape build

Comment 6

[Grace Bush]

Doug, 
Removing component registry allowed me to launch again (and use Profile Manager)-
on file/quit, the menu does not close and I have to reboot to remove it.

Comment 7

[Doug Turner (:dougt)]

I am not sure what you mean regarding the menu items.

Could you open up the component registry file with a text editor, and attach 
that?  The attachment does not load properly:

rename component registry to "component registry.txt"
Open it up with BBEdit, or a similar text editor.
save it as text and attach.

I am wondering if the problem how we save the relative paths on the mac. 

steve, can you reproduce this>?

Comment 8

[Grace Bush]

both builds - mozilla and commercial

If I remove the component.reg file in between launches I can relaunch and test 
ProfileManager functions.

I am not crashing or hanging on exit from either build now-cannot reproduce 
anyway.
If I do not remove the component.reg file I will see the behavior as noted 
below, splash screen comes up but app quits every time. 

I guess workaround is to remove component.reg- is no one else seeing this? 

Doug,
I tried opening component.reg file in simpletext - I get the message the file is 
too big. I do not have BBedit.  

Comment 9

[Steve Dagley]

Taking bug as I have the fix in my tree

Comment 10

[Steve Dagley]

Fix checked in (component names were being truncated in the rel: case causing 
them not to be found on 2nd launch)

Comment 11

[Grace Bush]

build 2000020708- mozilla build