Closed
Bug 19236
Opened 25 years ago
Closed 25 years ago
M11 Apprunner freezes at splash screen on Mac OS 9
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: MikeS, Unassigned)
Details
I tried to launch the M11 apprunner on Mac OS 9. On three attempts it caused a freeze at the Mozilla splash screen. The cursor will be active but clicks will not register and you can not execute a force quit or a soft system restart. I can bring up a debug prompt via command+power but once I input a single letter it will become a full freeze. (Note: I'm not a dev I just picked up the debug prompt tip) I thought Kaleidsoscope may have been a culprit so I disabled it at start-up and tried again to the same result. I gave mozilla more than 5 minutes to load before determineing it was a freeze. The mozilla registry in the prefs folder was not present nor was the Mozilla folder in the documents folder. I did not have the npjava plug-in in any netscape directories.
Comment 1•25 years ago
|
||
Reassigning all of leger's unscreened Browser-General bugs to nobody@mozilla.org for pre-screening and triage.
Comment 2•25 years ago
|
||
MikeS: Please try with the latest M13 nightly build and see if the problem is still there. Something that was wrong with M11 may have been fixed by now.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Comment 3•25 years ago
|
||
I can't find any related freezing bugs on the Mac platform, and this bug is for an old binary (M11), so I'm assigning a "worksforme" designation since the Mac builds are not freezing generally nowadays.
I did try M13 and the freeze is no longer present. I posted the bug in hopes that it would be resolved in a later build and that is was. You guys/gals are doing a great job and I'm sure the finished product will be spectacular. Mike S.
Old bug. 2000-03-14-12-M15 launched fine with OS9. Marking Verified.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•