Reminder bug to discuss and address this OSX specific issue. Mozilla & Netscape 6 Classic (for MacOS 8.6 & 9.x) ships with a Component Registry to reduce first launch startup time. Current Carbon builds don't include that file because it requires the app to be run once before packaging, but the carbon build refuses to run under 9.1 w/CarbonLib 1.4 (OS version currently installed on the carbon release build mac). I'll attach a macsbug log of the crash observed _immediately after_ component registration is complete. Steve says it should start up ok, even if browser and other functionalities might be broken under 9/carbonlib. Another approach suggested by Pink but that I'd rather avoid, is to resurrect the good ol' RegXPCOM, which caused us so much grief since day 1. I'd prefer to see Mozilla/Netscape be able to run _once_ just like we proceed for the Classic build. Other idea ? suggestions ?
Created attachment 53342 [details] Macsbug stdlog after running NS 6 Carbon on an OS9 machine. Crash occurs right after displaying "component registration finished" in the splash screen
Severity: normal → major
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Included pre-built Component Registry with OSX build → Include pre-built Component Registry with OSX builds
Target Milestone: --- → mozilla0.9.6
Hmm, nothing obvious from that stack trace but it looks bad. Any reason VM is turned on on that Mac? I know I've run the Carbon build under 9.x w/o crashing but I have never tried it with VM on (not that that should make a difference, it's just the only thing that comes to mind when looking at the log)
This has been fixed for a few days now. (crash was due to bugs profile on the system) A component registry is now included with daily builds (both mozilla & netscape)
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
marking verified based on jj's comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.