On a clobber Solaris/native build of a morning 6/28/99 CVS pull, apprunner crashes on startup. This happens when apprunner is trying to draw the UI for the first time. When it gets around to drawing the sidebar it crashes. This started happening about the time bug 8849 showed up. Unfortunately the removal of xpinstall from the build didn't fix the problem on solaris. The stack trace at the time of the crash is as follows. The mURLSpec that it is attempting to free is "0x3". current thread: t@1  _free_unlocked(0x3, 0x0, 0xfe031f98, 0x0, 0x0, 0x0), at 0xfdfc60d8  free(0x3, 0x7ca40, 0x0, 0x0, 0x0, 0x0), at 0xfdfc6088  PL_strfree(0x3, 0xfd38b57c, 0x9, 0x0, 0x0, 0xfe031f98), at 0xfe781d90 => RDFXMLDataSourceImpl::Init(this = 0x255614, uri = 0x560c80 "resource:/res/rdf/sidebar-browser.rdf"), line 635 in "nsRDFXMLDataSource.cpp"  0xff26b984(0x255614, 0x3, 0x1, 0xffbeddc0, 0x0, 0x0), at 0xff26b983  nsXPCWrappedNativeClass::CallWrappedMethod(this = 0x54f738, cx = 0x3b3e78, wrapper = 0x4655d8, desc = 0x46556c, callMode = CALL_METHOD, argc = 1U, argv = 0x4a2e68, vp = 0xffbee050), line 510 in "xpcwrappednativeclass.cpp"  WrappedNative_CallMethod(cx = 0x3b3e78, obj = 0x49c3a8, argc = 1U, argv = 0x4a2e68, vp = 0xffbee050), line 125 in "xpcwrappednativejsops.cpp"  js_Invoke(cx = 0x3b3e78, argc = 1U, constructing = 0), line 654 in "jsinterp.c"  js_Interpret(cx = 0x3b3e78, result = 0xffbee474), line 2215 in "jsinterp.c"  js_Invoke(cx = 0x3b3e78, argc = 2U, constructing = 0), line 670 in "jsinterp.c"  js_Interpret(cx = 0x3b3e78, result = 0xffbee8c4), line 2215 in "jsinterp.c"  js_Invoke(cx = 0x3b3e78, argc = 0, constructing = 0), line 670 in "jsinterp.c"  js_Interpret(cx = 0x3b3e78, result = 0xffbeeeec), line 2215 in "jsinterp.c"  js_Execute(cx = 0x3b3e78, chain = 0x2a05b8, script = 0x28b278, fun = (nil), down = (nil), debugging = 0, result = 0xffbeeeec), line 829 in "jsinterp.c"  JS_EvaluateUCScriptForPrincipals(cx = 0x3b3e78, obj = 0x2a05b8, principals = (nil), chars = 0x2b2660, length = 6U, filename = (nil), lineno = 0, rval = 0xffbeeeec), line 2584 in "jsapi.c"  JS_EvaluateUCScript(cx = 0x3b3e78, obj = 0x2a05b8, chars = 0x2b2660, length = 6U, filename = (nil), lineno = 0, rval = 0xffbeeeec), line 2566 in "jsapi.c"  JS_EvaluateScript(cx = 0x3b3e78, obj = 0x2a05b8, bytes = 0x55a660 "Boot()", length = 6U, filename = (nil), lineno = 0, rval = 0xffbeeeec), line 2533 in "jsapi.c"  GlobalWindowImpl::RunTimeout(this = 0x3b3df8, aTimeout = 0x41a988), line 1516 in "nsGlobalWindow.cpp"  nsGlobalWindow_RunTimeout(aTimer = 0x4e4c38, aClosure = 0x41a988), line 1433 in "nsGlobalWindow.cpp"  TimerImpl::FireTimeout(this = 0x4e4c38), line 73 in "nsTimer.cpp"  nsTimerExpired(aCallData = 0x4e4c38), line 196 in "nsTimer.cpp"  g_timeout_dispatch(0x286c40, 0xffbef1c8, 0x4e4c38, 0xfe3f1930, 0xfe3f1930, 0xffbef158), at 0xfe3cbaa0  g_main_dispatch(0xffbef1c8, 0xfe3f3d70, 0x0, 0xfe3f3cb0, 0xfe3f1930, 0x4), at 0xfe3ca7b4  g_main_iterate(0xffffffff, 0x1, 0xfe3cba4c, 0xfe3f3d78, 0xfe3f3ce0, 0xfe3f3d6c), at 0xfe3caee4  g_main_run(0x117b88, 0x117b88, 0xfe3f1930, 0xfe3f3d70, 0x91458, 0xfe43faa4), at 0xfe3cb0d8  gtk_main(0xfe4740a8, 0xfe67d5e0, 0xfe665b1c, 0x117b88, 0x0, 0xfe47105c), at 0xfe57baa8  nsAppShell::Run(this = 0x8d140), line 237 in "nsAppShell.cpp"  nsAppShellService::Run(this = 0x978f0), line 428 in "nsAppShellService.cpp"  main(argc = 1, argv = 0xffbef684), line 675 in "nsAppRunner.cpp"
Suspicious this might be a dup of (i.e., will be fixed by) 8016.
Per this post: news://news.mozilla.org/7lv64c%241jt1%40secnews.netscape.com Added jband and duncan to cc list.
Okay, after reading more of the followups to the above thread, I am convinced that this _has_ to be incorrect MI code for Solaris. Reassigning to rogerl. If I'm wrong, give it back.
So I have the MI bug fixed locally, but apprunner won't work for me - I can't even tell where it fails since gdb seg. faults, too. I can check theMI fix in if somebody wants to see if that fixes this problem???
Moving out to M10 per choffman's request
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Fixed (see 8016)
QA Contact massive update.
You need to log in before you can comment on or make changes to this bug.