Closed
Bug 140216
Opened 24 years ago
Closed 23 years ago
Composer opening crashes often [1.0 branch, @JS_GetPrivate]
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0.1
People
(Reporter: BenB, Assigned: bugzilla)
Details
(Keywords: crash)
Until recently, crash very often while Composer is in the process of being
opened. It happens fairly often, about every 3th or 4th time I open the
Composer, but not if I open a lot of Composers right after the start. It doesn't
matter, if I compose a new mail, reply or click on a mailto: link.
This is the 1.0 branch with Beonex Communicator modifications. (But it's
unlikely that it's Beonex-specific, more likely profile/setup-specific.)
I built a debug version and ran it in the debugger. Stack trace appended.
#0 JS_GetPrivate (cx=0x94fb810, obj=0x8569328)
at ../../../mozilla/js/src/jsapi.c:1911
#1 0x40dc57c2 in nsJSContext::ExecuteScript (this=0x8b03288,
aScriptObject=0x8569328, aScopeObject=0x88a8220, aRetValue=0x0,
aIsUndefined=0x0)
at ../../../../mozilla/dom/src/base/nsJSEnvironment.cpp:822
#2 0x41228715 in nsXULDocument::ExecuteScript (this=0x918cc10,
aScriptObject=0x8569328)
at ../../../../../mozilla/content/xul/document/src/nsXULDocument.cpp:6195
#3 0x41227bd3 in nsXULDocument::LoadScript (this=0x918cc10,
aScriptProto=0x8ccb0d8, aBlock=0xbffff3bc)
at ../../../../../mozilla/content/xul/document/src/nsXULDocument.cpp:5967
#4 0x41226295 in nsXULDocument::ResumeWalk (this=0x918cc10)
at ../../../../../mozilla/content/xul/document/src/nsXULDocument.cpp:5766
#5 0x41228491 in nsXULDocument::OnStreamComplete (this=0x918cc10,
aLoader=0x89b2938, context=0x0, aStatus=2152857618, stringLen=0,
string=0x40265c10 "")
at ../../../../../mozilla/content/xul/document/src/nsXULDocument.cpp:6145
#6 0x408a1560 in nsStreamLoader::OnStopRequest (this=0x89b2938,
request=0x8a7e4f0, ctxt=0x0, aStatus=2152857618)
at ../../../../mozilla/netwerk/base/src/nsStreamLoader.cpp:161
#7 0x409032ec in nsFileChannel::OnStopRequest (this=0x8a7e4f0,
request=0x8a6424c, context=0x0, aStatus=2152857618)
at ../../../../../mozilla/netwerk/protocol/file/src/nsFileChannel.cpp:480
#8 0x4088155a in nsOnStopRequestEvent::HandleEvent (this=0x89cad68)
at ../../../../mozilla/netwerk/base/src/nsRequestObserverProxy.cpp:212
#9 0x4088020f in nsARequestObserverEvent::HandlePLEvent (plev=0x89cad68)
at ../../../../mozilla/netwerk/base/src/nsRequestObserverProxy.cpp:115
#10 0x401cd3ce in PL_HandleEvent (self=0x89cad68)
at ../../../mozilla/xpcom/threads/plevent.c:596
#11 0x401cd20f in PL_ProcessPendingEvents (self=0x81abff8)
at ../../../mozilla/xpcom/threads/plevent.c:526
#12 0x401cf63c in nsEventQueueImpl::ProcessPendingEvents (this=0x8099020)
at ../../../mozilla/xpcom/threads/nsEventQueue.cpp:388
#13 0x409ee190 in event_processor_callback (data=0x8099020, source=22,
condition=GDK_INPUT_READ)
at ../../../../mozilla/widget/src/gtk/nsAppShell.cpp:184
#14 0x409edd8b in our_gdk_io_invoke (source=0x81773e0, condition=G_IO_IN,
data=0x81773d0) at ../../../../mozilla/widget/src/gtk/nsAppShell.cpp:77
#15 0x40563e10 in g_io_add_watch () from /usr/lib/libglib-1.2.so.0
#16 0x405654d8 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#17 0x40565ae3 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#18 0x40565c7c in g_main_run () from /usr/lib/libglib-1.2.so.0
#19 0x404867e7 in gtk_main () from /usr/lib/libgtk-1.2.so.0
#20 0x409eed85 in nsAppShell::Run (this=0x82091f8)
at ../../../../mozilla/widget/src/gtk/nsAppShell.cpp:364
#21 0x409a4f90 in nsAppShellService::Run (this=0x810a740)
at ../../../../mozilla/xpfe/appshell/src/nsAppShellService.cpp:308
#22 0x0805865b in main1 (argc=3, argv=0xbffffa54, nativeApp=0x8095af0)
at ../../../mozilla/xpfe/bootstrap/nsAppRunner.cpp:1415
#23 0x080593ed in main (argc=3, argv=0xbffffa54)
at ../../../mozilla/xpfe/bootstrap/nsAppRunner.cpp:1763
| Reporter | ||
Comment 1•24 years ago
|
||
s/Until/Since/ (don't know, when it started)
Keywords: crash,
mozilla1.0
Comment 2•24 years ago
|
||
build on w2k after 26Apr also has this problem. it crashed after the compose
window showed up.
Comment 3•24 years ago
|
||
build on 2002050108 is ok (on w2k) after latest spellcheck.xpi is installed.
| Assignee | ||
Comment 4•24 years ago
|
||
Ben, do you still have this problem?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0.1
| Reporter | ||
Comment 5•24 years ago
|
||
yes, it crashes even every 2nd or 3rd time. The first opening after starting
Mozilla seems to work all the time. A problem with the Composer "composting"
(reuse)?
| Reporter | ||
Comment 6•23 years ago
|
||
yeah, the bug is gone now in 1.0! :-)
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
using trunk builds 20021121 on winxp, macosx and linux I have not seen this
problem come back. I open compose windows several times a day on each if these
systems during routine testing. Verified.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•