Closed
Bug 185053
Opened 23 years ago
Closed 23 years ago
Crash if plugin is on a page and you "Quit Mozilla"
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 180366
People
(Reporter: bugzilla, Assigned: peterl-bugs)
Details
(Keywords: crash, stackwanted)
Attachments
(1 file)
|
2.61 KB,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130
When opening a page with a Carbon plugin, the plug-in runs normally. When you
close the page, then quit the browser, everything runs normally.
However, when you "Quit Mozilla" with the page containing the plug-in currently
open, Mozill closes the windows, as expected, but then crashes with the "Mozilla
has unexpectedly quit" message.
Reproducible: Always
Steps to Reproduce:
1.Compile the Scriptable Plugin Example with CodeWarrior 8.0
2.Place the plugin in the "Library:Internet Plug-Ins" folder
3.Open the Test html page
4.Select the "Quit Mozilla" menu item.
*BOOM*
Actual Results:
Mozilla closes open crowser windows and then gives the "Mozilla has unexpectedly
quit" message.
Expected Results:
Close up with no crash
Running on MacOSX v. 10.2.2, 512M RAM
Using the Scriptable plugin example in the source tree.
Plugin was compiled using Code Warrior 8.0 Carbon Version.
Comment 1•23 years ago
|
||
What's your stack? Are you seeing bug 180366?
The symptoms are very similar to 180366 except that there is no need to click on
anything. Just quit the browser and *crash*. Also the other difference is its
on the MacOSX and not XP (although this may not mean much if the problem is
related).
I am running it in the Mozilla 1.2 for MacOSX (production), so I will try to get
a stack dump w/o building the whole tree.
Updated•23 years ago
|
Keywords: crash,
stackwanted
Stack is here...I will upload the Crash log as well:
#0 0x03d7fee0 in 0x3d7fee0
#1 0x017e5aa8 in XPCWrappedNativeProto::_dt(void)
#2 0x017dee98 in DyingProtoKiller(JSDHashTable *, JSDHashEntryHdr *, unsigned
long, void *)
#3 0x0179278c in JS_DHashTableEnumerate
#4 0x017df490 in XPCJSRuntime::GCCallback(JSContext *, JSGCStatus)
#5 0x01f7c38c in jsds_GCCallbackProc(JSContext *, JSGCStatus)
#6 0x0248ae40 in DOMGCCallback(JSContext *, JSGCStatus)
#7 0x0174ef44 in js_GC
#8 0x0174e660 in js_ForceGC
#9 0x0172bcc0 in JS_GC
#10 0x024ae2a4 in nsDOMSOFactory::Observe(nsISupports *, char const *, wchar_t
const *)
#11 0x00284690 in nsObserverService::NotifyObservers(nsISupports *, char const
*, wchar_t const *)
#12 0x002a7a44 in NS_ShutdownXPCOM
#13 0x001a4d20 in main
Comment 6•23 years ago
|
||
*** This bug has been marked as a duplicate of 180366 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•