Closed Bug 196471 Opened 22 years ago Closed 22 years ago

Mozilla crashes on launch/startup every time

Categories

(Core Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 202619

People

(Reporter: jim, Assigned: peterlubczynski-bugs)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/4.0 (compatible; MSIE 5.12; Mac_PowerPC) Build Identifier: Camino crashes about 5-10 seconds after launching. I trashed all prefs and reinstalled with no change. The window shows, I can click a button and it changes color, but nothing can alter Camino's crash course. Several TalkBack reports have been sent. Reproducible: Always Steps to Reproduce: 1.Launch Camino 2.Wait 3.Cry Actual Results: Camino crashed Expected Results: Camino should have launched normally and allowed me to browse the web. My Machine is a Power Mac 9500, 180MHz 604e, with 128MB of RAM and a little under 30 gigs of storage on one Maxtor ATA/66 drive, connected to an ACARD AEC-6260M PCI ATA-66 controller. OS is 10.1, rev. 5G64. I'd like to thank Ryan Rempel, and Other World Computing, for their utility XPostFacto, which allowed my to install OS X on my Mac. That's all!
Chimera 0.6 works just fine on the identical setup. - Jordan
Reporter, which build is it that you are having this problem ?
Finder Get Info reports Camino 0.7.0, created Thursday, March 6, 2003, at 6:33 P.M. I don't know how to get any more specifics, since I can't actually use the program.
Both the milestone build: ftp://ftp.mozilla.org/pub/camino/releases/Camino-0.7.dmg.gz and the nightly builds work for me on start up: ftp://ftp.mozilla.org/pub/camino/nightly/2003-03-09-07
something had to change between 0.6 and 0.7 which caused this...I just updated to 10.1.5, build 5S60b, and the problem remains. I'll grab a nightly build when I have a chance and report back.
Jordan, please provide a representative TalkBack report ID.
downgrading from blocker to critical until we get more reports of this.
Severity: blocker → critical
Talkback ID's: TB189132M TB191055K TB196694M
I get an error message "The Operation Could not be completed An Unexpected error occurred (error code 1000)" Instantly when trying to launch the 20030316 build.
I should add that the 0.7 build works fine, as did the build prior to 20030316 (I think)
I also get this. The final 0.70 from the 1.0.1 branch worked fine. Every nightly build I've tried since then (I initially waited for a week of so to let the smoke clear before attempting NB's based on the new branch) ends immediately -- no crash, no dump, only info is the small window displaying: "The Operation Could not be completed An Unexpected error occurred (error code 1000)" It appears to not get far enough to initiate any kind of Talkback.
TB206950Y - most recent ID I don't get an error #, just unexpectedly quit.
does this still happen?
Assignee: saari → pinkerton
Target Milestone: --- → Camino0.8
Yes it does still happen. I just updated from 10.1 to 10.2 and it still still happens. I tried the nightly build the day after Comment #13 and it still happens.
Camino 0.7 works as intended on my Sawtooth G4 running 10.2. The 9500 got parted out. Sorry I can't help you troubleshoot this further. Fortunately, it looks like there's some other users who can. Jordan
i'm having issues getting to the talkback server. can you go into the console app and turn on crash reporter (in the preferences) and then the next time camino crashes, you'll get a log from the console. please attach that log here so i can see where it's crashing. thanks!
stack from chris: Thread 0 Crashed: #0 0x0064d0a8 in nsPluginFile::FreePluginInfo(nsPluginInfo&) #1 0x00390f20 in nsPluginHostImpl::ScanPluginsDirectory(nsIFile*, nsIComponentManager*, int, int*, int) #2 0x003911b4 in nsPluginHostImpl::ScanPluginsDirectoryList(nsISimpleEnumerator*, nsIComponentManager*, int, int*, int) #3 0x003914b0 in nsPluginHostImpl::FindPlugins(int, int*) #4 0x0039126c in nsPluginHostImpl::LoadPlugins() #5 0x00390204 in nsPluginHostImpl::GetPluginFactory(char const*, nsIPlugin**) #6 0x00195964 in nsJVMManager::StartupJVM() #7 0x00196084 in nsJVMManager::MaybeStartupLiveConnect() #8 0x00791fd0 in nsJVMManager::StartupLiveConnect(JSRuntime*, int&) #9 0x0007da04 in nsJSEnvironment::Init() #10 0x0007dc5c in NS_CreateScriptContext(nsIScriptGlobalObject*, nsIScriptContext**) #11 0x0045d970 in nsDocShell::EnsureScriptEnvironment() #12 0x00111a48 in nsWebShell::GetInterface(nsID const&, void**) #13 0x05077704 in nsGetInterface::operator()(nsID const&, void**) const #14 0x05075d64 in nsCOMPtr_base::assign_from_helper(nsCOMPtr_helper const&, nsID const&) #15 0x000740c8 in nsWebBrowser::GetContentDOMWindow(nsIDOMWindow**) #16 0x00075c98 in nsWebBrowser::Create() #17 0x00017b14 in -[CHBrowserView initWithFrame:]
I've realised now that no recent Mozilla builds at all work on my machine. Since I was using Camino at the time, my builds of Mozilla and Netscape were older, and they worked. So: Mozilla 1.3 alpha (december 2002) works. Netscape 7.01 (November 2002) works The most recent builds of both crash on startup. Camino fails since at least Chimera 0.6.0 2003-03-04, but I'm darned sure that back in March I was successfully using Camino 0.6.0, so maybe this is all a red herring.
Mea Culpa. Well, not me exactly, but the errant plugin in my case was Omnis Studio webclient.plugin of April 22 this year. Removing it, Camino now launches fine. Thanks, Chris
for starters, this is a mozilla bug if anything. however, can someone try to contact omnigroup about this plugin?
Assignee: pinkerton → peterlubczynski-bugs
Component: General → Plug-ins
Product: Camino → Browser
QA Contact: winnie → bmartin
Target Milestone: Camino0.8 → ---
Version: unspecified → Trunk
peterl: this affects both camino and mozilla. not sure if it's omni's issue or not
Flags: blocking1.5b?
Keywords: stackwanted
Summary: Camino crashes on launch/startup every time → Mozilla crashes on launch/startup every time
*** This bug has been marked as a duplicate of 202619 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.5b?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.