Closed Bug 149618 Opened 22 years ago Closed 22 years ago

Mozilla locks up on launch at "loading nsDialogHelperApp.js"

Categories

(SeaMonkey :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dkmiller, Assigned: Matti)

Details

(Keywords: hang)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
BuildID:    20020605

Mozilla 1.0rc1 worked fine on my Power Mac beige G3/266 with 416 MB of RAM and
Mac OS 10.1.4 (and 10.1.5 as well). But when I overwrote the Mozilla folder with
the final Mozilla 1.0, the new version would not launch. The splash screen comes
up, but locks up when loading nsDialogHelperApp.js (at least that's what's
listed when it locks up).

I get the SPOD (spinning pizza of death) and have to force quit Mozilla or kill
the process to get it to go away. Other processes remain unaffected, but I can't
log out or restart until I kill Mozilla. I was running 1.0rc1 with the "Pinball"
chrome skin, if that makes any difference -- that all works fine on a Win 98 PC
upstairs.

Reinstalling 1.0rc1 means Mozilla loads fine, so it's something new between rc1
and the final release. I noticed the same problem with Netscape 7.0 PR1, so it
may be in rc2 or rc3 where the bug first appeared.

Reproducible: Always
Steps to Reproduce:
1. Install Mozilla 1.0 final on Mac OS X
2. Launch it
3. Wait and wait and wait. :)

Actual Results:  Lock up.

Expected Results:  Launch!

Power Mac Beige G3/266 Rev A (1997)
Mac OS X 10.1.4 and 10.1.5
Mozilla is default browser
Pinball chrome theme installed as default
Derek, can you reproduce this problem using a new Mozilla user profile?

Otherwise, use the Sampler application (included in the OS X Developer Tools) to sample Mozilla for 5 
seconds or so while this hang is occurring. Attach the results hereon.
Keywords: hang
Creating a new user profile did the trick. Everything works okay now, and I copied
over bookmarks, cookies, and certificates without incident.

So something was corrupt in my old profile, I guess, but the source of that
problem remains a mystery.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.