395552 - Chrome Registration failure and crash @0x131799c on first run of newer (20070908) SM2 trunk build

Status: RESOLVED DUPLICATE of bug 371298

(SeaMonkey :: Build Config, defect)

Description

[Rich Gray (:rbgray)]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a8pre) Gecko/2007090801 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a8pre) Gecko/2007090801 SeaMonkey/2.0a1pre

Upgraded from the 20070901 official nightly build to 20070908 and got

Chrome Registration Failed

SeaMonkey couldnot install this item because of a
failure in Chrome Registration. Please contact the
author about this problem.

( OK )

twice, followed by a crash.   A subsequent restart comes up cleanly without error.



Reproducible: Always

Steps to Reproduce:
1. start clean (not trusting myself to totally nuke all data, I made new accounts)
2. install, run & quit a pre 20070908 build, such as the 20070901 nightly.
3. install and run 200708
Actual Results:  
Two occurrences of the "Chrome Registration Failure" alert, followed by a crash.

Expected Results:  
Normal start up.

After the crash in my working account, I reproduced this by twice starting in a new standard (non-admin) user account, and stepping through the nightlies from   
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2007-09-01-01-trunk/seamonkey-2.0a1pre.en-US.mac.dmg through
http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2007-09-08-01-trunk/seamonkey-2.0a1pre.en-US.mac.dmg .  

Reproducibly got the failure messages and crash when I got to the 20070908 build.  The most recent crash dump is:
http://crash-stats.mozilla.com/report/index/5f35a366-5e6b-11dc-ba67-001a4bd43e5c?date=2007-09-09-00

There was suspicion in #seamonkey that this may be a venkman.jar problem, and indeed, the Javascript Debugger is missing from Tools > Web Development.

Comment 1

[Rich Gray (:rbgray)]

Noticed that Chatzilla is also missing.  That would explain TWO chrome registration failures before the crash.

This turns out to not be a function of any particular build, but rather .app writability as covered in Bug 371298.  I will comment further there on the specific scenarios which can lead to this situation in OS X.

Marking as a duplicate of bug 371298.