Closed
Bug 7861
Opened 25 years ago
Closed 25 years ago
Crash on exit (stack trace included)
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
M7
People
(Reporter: dp, Assigned: rogerl)
Details
Looks like memory corruption at its peak.
#0 0x407e06a1 in __kill ()
#1 0x407e04cf in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x407e16df in abort () at ../sysdeps/generic/abort.c:83
#3 0x40491baf in JS_Assert (s=0x40497fd1 "root_points_to_gcArenaPool",
file=0x40497faf "jsgc.c", ln=603) at jsutil.c:130
#4 0x40442360 in gc_root_marker (he=0x84d7028, i=210, arg=0x80efc38)
at jsgc.c:603
#5 0x40443879 in JS_HashTableEnumerateEntries (ht=0x80f1e08,
f=0x404422a4 <gc_root_marker>, arg=0x80efc38) at jshash.c:347
#6 0x404425c5 in js_GC (cx=0x80f2338) at jsgc.c:724
#7 0x404423c8 in js_ForceGC (cx=0x80f2338) at jsgc.c:618
#8 0x4041b4f7 in JS_GC (cx=0x80f2338) at jsapi.c:984
#9 0x403775cd in nsJSContext::GC (this=0x80f2318) at nsJSEnvironment.cpp:329
#10 0x4037760b in nsJSContext::ScriptEvaluated (this=0x80f2318)
at nsJSEnvironment.cpp:340
#11 0x4039e579 in nsJSEventListener::HandleEvent (this=0x82944a0,
aEvent=0x8703dc8) at nsJSEventListener.cpp:98
#12 0x40d11bc6 in nsEventListenerManager::HandleEvent (this=0x82941d0,
aPresContext=@0x80e2780, aEvent=0xbfffee10, aDOMEvent=0xbfffedd4,
aFlags=3, aEventStatus=@0xbffff0c8) at nsEventListenerManager.cpp:569
#13 0x40ade7e2 in RDFElementImpl::HandleDOMEvent (this=0x8293948,
aPresContext=@0x80e2780, aEvent=0xbfffee10, aDOMEvent=0xbfffedd4,
aFlags=1, aEventStatus=@0xbffff0c8) at nsRDFElement.cpp:2275
#14 0x40d14403 in nsEventStateManager::CheckForAndDispatchClick (
this=0x82631c8, aPresContext=@0x80e2780, aEvent=0xbffff148,
aStatus=@0xbffff0c8) at nsEventStateManager.cpp:596
#15 0x40d134d2 in nsEventStateManager::PostHandleEvent (this=0x82631c8,
aPresContext=@0x80e2780, aEvent=0xbffff148, aTargetFrame=0x829a610,
aStatus=@0xbffff0c8, aView=0x8150670) at nsEventStateManager.cpp:168
#16 0x40d4e713 in PresShell::HandleEvent (this=0x81542f0, aView=0x8150670,
aEvent=0xbffff148, aEventStatus=@0xbffff0c8) at nsPresShell.cpp:2030
#17 0x41082a27 in nsView::HandleEvent (this=0x8150670, event=0xbffff148,
aEventFlags=28, aStatus=@0xbffff0c8, aHandled=@0xbffff05c)
at nsView.cpp:832
#18 0x4108bc2f in nsViewManager::DispatchEvent (this=0x80f2040,
aEvent=0xbffff148, aStatus=@0xbffff0c8) at nsViewManager.cpp:1739
#19 0x41080af8 in HandleEvent (aEvent=0xbffff148) at nsView.cpp:66
#20 0x400edeb6 in nsWidget::DispatchEvent (this=0x81506d8, event=0xbffff148,
aStatus=@0xbffff104) at nsWidget.cpp:997
#21 0x400eddc0 in nsWidget::DispatchWindowEvent (this=0x81506d8,
event=0xbffff148) at nsWidget.cpp:959
#22 0x400edf6c in nsWidget::DispatchMouseEvent (this=0x81506d8,
aEvent=@0xbffff148) at nsWidget.cpp:1024
#23 0x400ee8ef in nsWidget::OnButtonReleaseSignal (this=0x81506d8,
aGdkButtonEvent=0x80edd70) at nsWidget.cpp:1522
#24 0x400ef0e6 in nsWidget::ButtonReleaseSignal (aWidget=0x8150890,
aGdkButtonEvent=0x80edd70, aData=0x81506d8) at nsWidget.cpp:1759
#25 0x4062cc49 in gtk_marshal_BOOL__POINTER ()
#26 0x405ee915 in gtk_handlers_run ()
#27 0x405edc8e in gtk_signal_real_emit ()
#28 0x405ebc5f in gtk_signal_emit ()
#29 0x40623928 in gtk_widget_event ()
#30 0x405bf5e2 in gtk_propagate_event ()
#31 0x405be768 in gtk_main_do_event ()
#32 0x40668c8b in gdk_event_dispatch ()
#33 0x40696dd2 in g_main_dispatch ()
#34 0x406973bb in g_main_iterate ()
#35 0x40697571 in g_main_run ()
#36 0x405be15b in gtk_main ()
#37 0x400e0071 in nsAppShell::Run (this=0x809fe88) at nsAppShell.cpp:197
#38 0x400217a1 in nsAppShellService::Run (this=0x8094b10)
at nsAppShellService.cpp:402
#39 0x804b1cc in main (argc=1, argv=0xbffff770) at nsAppRunner.cpp:556
(gdb)
Updated•25 years ago
|
Assignee: mccabe → rogerl
Comment 1•25 years ago
|
||
Roger, can you take a look at this?
Assignee | ||
Comment 2•25 years ago
|
||
Umm, possible perhaps to get a clue about what was run on what platform?
Reporter | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•25 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•