Closed
Bug 253804
Opened 21 years ago
Closed 21 years ago
"Check for new messages at startup" crashes if Inbox summary .msf file is corrupted [@ nsPop3Sink::FindPartialMessages ]
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: relf, Assigned: Bienvenu)
Details
(Keywords: crash, fixed-aviary1.0, Whiteboard: TB456362K)
Crash Data
Attachments
(1 file)
679 bytes,
patch
|
mscott
:
superreview+
|
Details | Diff | Splinter Review |
Linux build 2004072806
The crash occurs on MailNews startup if "Check for new messages at startup" is
on and Inbox summary (.msf) file is corrupted.
I found the following workaround:
1. Switch browser to Offline
2. Open MailNews
3. Click on the problematic account Inbox and allow MailNews to reconstruct
Summary file
4. Switch Browser/MailNews back to Online
5. Check for new messages
I have a talkback incident record for the crash but TalkBack fails to send it.
Talkback reports "Network Error: Receive Failed". No idea what that means. Other
network applications are working fine.
Comment 1•21 years ago
|
||
(In reply to comment #0)
> I have a talkback incident record for the crash but TalkBack fails to send it.
> Talkback reports "Network Error: Receive Failed". No idea what that means.
> Other network applications are working fine.
I assume that means the Talkback server is down. The message is stored in the
Talkback profile of this browser, and sending will be retried next time you
start that browser online. It won´t be sent if you install and use another nightly.
On windows, if I start talkback.exe in the components folder, I can see the
queued messages waiting to be sent, and I also can start sending.
Updated•21 years ago
|
Keywords: talkbackid
Assignee | ||
Comment 3•21 years ago
|
||
confirming for investigation - this works for me, but I'll try it some more. I
assume INBOX.msf is out of date, and not actually corrupted...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•21 years ago
|
||
stack:
nsPop3Sink::FindPartialMessages()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/mailnews/local/src/nsPop3Sink.cpp,
line 692]
nsPop3Sink::BeginMailDelivery()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/mailnews/local/src/nsPop3Sink.cpp,
line 329]
nsPop3Protocol::GetStat()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/mailnews/local/src/nsPop3Protocol.cpp,
line 1763]
nsPop3Protocol::ProcessProtocolState()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/mailnews/local/src/nsPop3Protocol.cpp,
line 3492]
nsMsgProtocol::OnDataAvailable()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/mailnews/base/util/nsMsgProtocol.cpp,
line 660]
nsInputStreamPump::OnStateTransfer()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/netwerk/base/src/nsInputStreamPump.cpp,
line 710]
nsInputStreamPump::OnInputStreamReady()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/netwerk/base/src/nsInputStreamPump.cpp,
line 339]
nsInputStreamReadyEvent::EventHandler()
PL_HandleEvent()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/plevent.c,
line 692]
PL_ProcessPendingEvents()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/plevent.c,
line 627]
nsEventQueueImpl::ProcessPendingEvents()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/threads/nsEventQueue.cpp,
line 395]
event_processor_callback()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 191]
our_gdk_io_invoke()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 78]
libglib-1.2.so.0 + 0xea56 (0x40291a56)
libglib-1.2.so.0 + 0x1003d (0x4029303d)
libglib-1.2.so.0 + 0x104f4 (0x402934f4)
libglib-1.2.so.0 + 0x10724 (0x40293724)
libgtk-1.2.so.0 + 0xa025f (0x4019f25f)
nsAppShell::Run()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/widget/src/gtk/nsAppShell.cpp,
line 322]
nsAppShellService::Run()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/appshell/src/nsAppShellService.cpp,
line 489]
main1()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 710]
main()
[/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpfe/bootstrap/nsAppRunner.cpp,
line 1801]
libc.so.6 + 0x157f8 (0x403ba7f8)
This is the only crasher that TB reports with that stack
Keywords: talkbackid
Summary: "Check for new messages at startup" crashes if Inbox summary .msf file is corrupted → "Check for new messages at startup" crashes if Inbox summary .msf file is corrupted [@ nsPop3Sink::FindPartialMessages ]
Assignee | ||
Comment 5•21 years ago
|
||
basically check for null parser
Assignee | ||
Updated•21 years ago
|
Attachment #155064 -
Flags: superreview?(mscott)
Updated•21 years ago
|
Attachment #155064 -
Flags: superreview?(mscott) → superreview+
Assignee | ||
Comment 6•21 years ago
|
||
should be fixed now.
Reporter | ||
Comment 7•21 years ago
|
||
The crash has indeed gone. But there is still some consequences. See bug 254947
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
Updated•14 years ago
|
Crash Signature: [@ nsPop3Sink::FindPartialMessages ]
You need to log in
before you can comment on or make changes to this bug.
Description
•