It's odd that this has'n been reported. Have to file a bug before I can consider fixing it. Early in application launch, after building (or installing, once the installer has fully implemented chrome installation), Mozilla will crash in a char [] destructor within ProcessNewChrome. The problem is heap corruption because strtok behaves differently on the Mac. The fix will be to not use strtok.

Is this with commercial or mozilla specific build? gbush, do you see this?

It affects both mozilla and netscape builds. Oddly, it only seems to happen on certain Macintoshes -- it happens on mine every time without fail. It never happens on saari's. It probably hasn't started happening on installed builds yet, but expect it to as soon as the installer team have chrome installation fully implemented; a feature I think is due to land any day now. It must not happen on most developer's machines, else someone would have written this bug sooner. But it's quite reliable on some.

I have not seen this on my 8.5.1 machine- but I am familiar with having one or two Mac machines behaving differently than all the rest.

dogfood for danm...putting on [dogfood+] radar.

processing of new chrome registration is now more robust.

verified fixed (a.k.a. what danm said [since this was only happening on some development builds on mac]).