Closed Bug 134097 Opened 23 years ago Closed 22 years ago

always crash opening mail after purging msgs (profile corruption?)

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 149059
mozilla1.0

People

(Reporter: bugzilla, Assigned: sspitzer)

References

Details

(Whiteboard: needinfo: QL on Linux?,[ADT2])

found using 2002.03.26.08 linux comm bits on linux rh7.2, although i think the particular build might not be relevant. when i recently accessed my mail, i got dlg warnings that my disk quota for mail on the IMAP server was reached. in an automated mail i rec'd, i was told to remove msgs, with the suggestion to visit http://nsmail-2.mcom.com/ for more info... anyhow here's what i did (from what i can recall): 1. in the n6.x mail client, i attempted to delete a few messages with large attachments as well as empty out some folders that had a huge amount of (mostly unread) messages. i cannot remember whether it was when i clicked to view the message or folder contents, or right after i had hit Delete to remove them, but i kept getting those nagging "you've exceeding your mail disk quota" warnings. but when i emptied the Trash, the messages seemed to have gone away... 2. however, when i went to view another message or folder (after emptying trash), i kept getting the nag warning. so, i went to http://nsmail-2.mcom.com/ to see what info i can find... 3. unfortunately, that page wouldn't load in n6.x. so, i fired up communicator 4.7x and managed to login there. 4. i noticed that one of messages supposedly removed in (1) was still there, so, i deleted it again from http://nsmail-2.mcom.com/ --i also did a bit of minor cleanup by deleting an old mail folder or two. 5. when i was done, i logged out and quit 4.7x. 6. went back to mail in n6.x and clicked Get New Msgs button. results: crash. 7. restarted n6.x, selected Tasks > Mailnews, logged in... results: crashed again. ...wash, rinse, repeat: i could no longer access my mail. i've tried removing the .msf files, the panacea.dat, localstore.rdf, XUL.mfasl, but i still keep crashing when opening files. short of creating a new profile, are there other possible workarounds? note: this is not a problem with a new profile, nor was it a problem on win2k with an older profile...so some sort of corruption is going on, methinks. the talkback reports for getting new msgs and opening mail are the same: libc.so.6 + 0x85b3a (0x40542b3a) nsMsgIMAPFolderACL::BuildInitialACLFromCache() nsMsgIMAPFolderACL::nsMsgIMAPFolderACL() nsImapMailFolder::GetFolderACL() nsImapMailFolder::GetCanFileMessages() nsImapMailFolder::MoveIncorporatedMessage() nsImapMailFolder::ApplyFilterHit() nsMsgFilterList::ApplyFiltersToHdr() nsImapMailFolder::NormalEndHeaderParseStream() XPTC_InvokeByIndex() EventHandler() PL_HandleEvent() PL_ProcessPendingEvents() nsEventQueueImpl::ProcessPendingEvents() event_processor_callback() our_gdk_io_invoke() libglib-1.2.so.0 + 0xff9e (0x40390f9e) libglib-1.2.so.0 + 0x11773 (0x40392773) libglib-1.2.so.0 + 0x11d39 (0x40392d39) libglib-1.2.so.0 + 0x11eec (0x40392eec) libgtk-1.2.so.0 + 0x94333 (0x402ae333) nsAppShell::Run() nsAppShellService::Run() netscape-bin + 0x84e9 (0x080504e9) netscape-bin + 0x8cc7 (0x08050cc7) libc.so.6 + 0x1c507 (0x404d9507)
this might be a topcrash. I'll debug with sarah on her machine soon.
Status: NEW → ASSIGNED
Keywords: nsbeta1
Mail News bug team needs to know if this happens on Windows.
Whiteboard: needinfo
My steps to reproduce on Linux - no crash: 1. With opened current build N6, I open Comm 4.7. 2. Using the same account in both clients: I delete some messages from Comm 4.7. 3. Quit Comm 4.7. 4. Come back to our N6, the same account. Check new messages, read them, go to another folder. Another combination - not to quit Comm 4.7 and come back to our N6. No problem. The same steps to check on Win2K - no problem.
This could be profile specific (i.e. profile got into a state to run into this). cc: some folks from talkback team to see if this is a topcrash. Would an IMAP log help here, David/Seth? If so, we can direct sairuh to obtain one.
using a mozilla debug on linux (from last night), i don't crash using the same profile i used as originally reported. also, when i then tested the profile using 2002.04.04.10 commercial linux bits, i didn't crash either. hmmm...
Summary: always crash opening mail after purging msgs → always crash opening mail after purging msgs (profile corruption?)
see bug 128386 for possible steps to recreate this problem.
Seth, why do you think this is related to QuickLaunch, which is only on Windows?
Whiteboard: needinfo → needinfo: QL on Linux?
That was me (bienvenu) that thought it was related. The stack traces are exactly the same, and it's a very odd stack trace for a crash - it's a bit hard to explain without going down to the code level but suffice it to say that it has to be something very weird going on to crash there, and the odds are stacked against there being two weird things going on causing this crash - it might be that there's a profile corruption that's easy to recreate with quick launch and not so easy otherwise. I haven't verified that bug 128386 is really recreatable and generates this crash but I'll try.
Discussed in Mail News bug mtg with Engineering QA and PjM. Decided to ADT2 and plus this bug.
Keywords: nsbeta1nsbeta1+
Whiteboard: needinfo: QL on Linux? → needinfo: QL on Linux?,[ADT2]
Target Milestone: --- → mozilla1.0
per mail news bug mtg, plus is contingent on bug 128386 being usable to reproduce this
bug 128386 works for me - I thought it might be Cavin's recent checkin to null out the server pointer when shutting down, but I commented that out and still could not recreate bug 128386 - perhaps some other fix went in? I think this should be wfm, since sairuh can't reproduce it either now. marking wfm.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Verified wfm on recent trunk builds.
Status: RESOLVED → VERIFIED
reopening to dup correctly
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
dup of 149059 *** This bug has been marked as a duplicate of 149059 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago22 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.