Closed
Bug 20275
Opened 25 years ago
Closed 25 years ago
[superwindow] crash when reading mail
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: sspitzer, Assigned: blizzard)
Details
chris, I got an abort in the super window code. here's the stack trace.
#0 0x402bb111 in __kill ()
#1 0x40209f7b in raise (sig=6) at signals.c:63
#2 0x402bc447 in abort () at ../sysdeps/generic/abort.c:88
#3 0x407ae103 in g_logv ()
#4 0x407ae1c6 in g_log ()
#5 0x406415cf in gdk_superwin_new (parent_window=0x891a3d8, x=0, y=0,
width=578, height=350) at gdksuperwin.c:124
#6 0x4061a39e in nsWindow::CreateNative (this=0x85550a8,
parentWidget=0x883ed90) at nsWindow.cpp:976
#7 0x40614159 in nsWidget::CreateWidget (this=0x85550a8, aParent=0x0,
aRect=@0xbffff020, aHandleEventFunction=0x4138c1b0 <HandleEvent(nsGUIEvent *)>,
aContext=0x883eaf8, aAppShell=0x0, aToolkit=0x0, aInitData=0x0,
aNativeParent=0x883ed90) at nsWidget.cpp:1103
#8 0x406143a0 in nsWidget::Create (this=0x85550a8, aParent=0x883ed90,
aRect=@0xbffff020, aHandleEventFunction=0x4138c1b0 <HandleEvent(nsGUIEvent *)>,
aContext=0x883eaf8, aAppShell=0x0, aToolkit=0x0, aInitData=0x0) at
nsWidget.cpp:1213
#9 0x4138ecfa in nsView::CreateWidget (this=0x850ea50, aWindowIID=@0x411f98e8,
aWidgetInitData=0x0, aNative=0x883ed90, aEnableDragDrop=1) at nsView.cpp:1261
#10 0x4111af5c in DocumentViewerImpl::MakeWindow (this=0x825a8f0,
aNativeParent=0x883ed90, aBounds=@0xbffff34c,
aScrolling=nsScrollPreference_kAuto) at nsDocumentViewer.cpp:822
#11 0x41119214 in DocumentViewerImpl::Init (this=0x825a8f0,
aNativeParent=0x883ed90, aDeviceContext=0x883eaf8, aPrefs=0x80e55a8,
aBounds=@0xbffff34c, aScrolling=nsScrollPreference_kAuto) at
nsDocumentViewer.cpp:424
#12 0x40a34bb6 in nsWebShell::Embed (this=0x8937868, aContentViewer=0x825a8f0,
aCommand=0x8987b90 "view", aExtraInfo=0x0) at nsWebShell.cpp:887
#13 0x40a322b4 in nsDocumentBindInfo::OnStartRequest (this=0x82860c8,
channel=0x8a1ee00, ctxt=0x0) at nsDocLoader.cpp:1360
#14 0x40a32fbd in nsChannelListener::OnStartRequest (this=0x84eb8d8,
aChannel=0x8a1ee00, aContext=0x0) at nsDocLoader.cpp:1550
#15 0x40593057 in nsFileChannel::OnStartRequest (this=0x8a1ee00,
transportChannel=0x8a34ba8, context=0x0) at nsFileChannel.cpp:465
#16 0x40553cf2 in nsOnStartRequestEvent::HandleEvent (this=0x8514b20) at
nsAsyncStreamListener.cpp:245
#17 0x405537ca in nsStreamListenerEvent::HandlePLEvent (aEvent=0x8a82650) at
nsAsyncStreamListener.cpp:173
#18 0x401b236b in PL_HandleEvent (self=0x8a82650) at plevent.c:537
#19 0x401b227c in PL_ProcessPendingEvents (self=0x80a76f8) at plevent.c:498
#20 0x40168a59 in nsEventQueueImpl::ProcessPendingEvents (this=0x80a76d0) at
nsEventQueue.cpp:193
#21 0x405fcc9c in event_processor_callback (data=0x80a76d0, source=8,
condition=GDK_INPUT_READ) at nsAppShell.cpp:233
#22 0x405fc5af in our_gdk_io_invoke (source=0x8258ee0, condition=G_IO_IN,
data=0x823e568) at nsAppShell.cpp:54
#23 0x407aa3ca in g_io_unix_dispatch ()
#24 0x407aba86 in g_main_dispatch ()
#25 0x407ac041 in g_main_iterate ()
#26 0x407ac1e1 in g_main_run ()
#27 0x406d57a9 in gtk_main ()
#28 0x405fd295 in nsAppShell::Run (this=0x80bb678) at nsAppShell.cpp:404
#29 0x403c2bf1 in nsAppShellService::Run (this=0x80a73b8) at
nsAppShellService.cpp:488
#30 0x804c6b4 in main1 (argc=1, argv=0xbffff9e4) at nsAppRunner.cpp:588
#31 0x804c959 in main (argc=1, argv=0xbffff9e4) at nsAppRunner.cpp:638
#32 0x402b4cb3 in __libc_start_main (main=0x804c7bc <main>, argc=1,
argv=0xbffff9e4, init=0x804a930 <_init>, fini=0x80518a8 <_fini>,
rtld_fini=0x4000a350, stack_end=0xbffff9dc) at
../sysdeps/generic/libc-start.c:78
does this match anything else you've seen?
opening this bug in case I see it again.
I don't know how to reproduce it.
this abort happened when I was either switching between messages in a folder, or
delete a message (which would cause it to switch between messages).
sorry I don't have more exact info.
Updated•25 years ago
|
Severity: normal → major
Comment 1•25 years ago
|
||
Same thing happens to me, on Linux build 1999.11.28.08, but doesn't happen on
1999.11.15.20 (M11). It happens whenever I select or delete more than two
messages quickly in a row, before the message has a chance to load completely.
Very annoying, especially when deleting a few messages in a row.
Comment 2•25 years ago
|
||
To reproduce:
1. Open IMAP mail folder
2. Select a message
3. Click delete after the header loads, but before the message text is displayed
You see the next message being selected, then Mozilla crashes, complaining:
** ERROR **: file gdksuperwin.c: line 124 (gdk_superwin_new): assertion failed:
(superwin->shell_window)
aborting...
The message is not deleted. If you click delete before the header is displayed,
or after the message body is displayed, it works.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•25 years ago
|
||
How old is this build? I checked in code yesterday at about 1:30 pm pacific
time that should have prevented this problem.
Reporter | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•25 years ago
|
||
my build was before your check in.
since you feel it has been fixed, I'll mark it fixed, and re-open if we see the
crasher again.
so far, I'm not seeing in on my build today.
zach - do you mind helping me verify this bug since you have consistently
reproducible steps? Since the check in was yesterday, perhaps you can try it
with a build from today or tomorrow? If you can help, it's much appreciated.
Thanks.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
Yes, works fine on 1999.11.30.08 Linux build.
Assignee | ||
Comment 7•25 years ago
|
||
I'd just like to note that if anyone sees this assertion again and can reproduce
it easily, please let me know. This is a tricky problem.
Assignee | ||
Comment 8•25 years ago
|
||
Please ignore the spam. Changing address.
Assignee: blizzard → blizzard
Status: VERIFIED → NEW
Assignee | ||
Comment 9•25 years ago
|
||
bustage from my reassign
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•