Closed Bug 81535 Opened 23 years ago Closed 23 years ago

Crash when collapse/expand/select in offline state.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Other
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 81273

People

(Reporter: laurel, Assigned: sspitzer)

Details

Attachments

(1 file)

Using may17 commercial trunk build, win98 I'm not sure exactly who this might belong to, but I've hit this crash a few times when expanding/collapsing hierarchies in a multiple account profile and selecting folders... no exact steps, but have been able to crash several times. I cannot make this crash happen when online, only when I've been in the offline state. General scenario/steps: (sorry if the description goes a bit overboard) 1. I have a multiple account profile: a couple IMAP accounts, a POP account, a couple webmail accounts, a news account and an AOL account. The main IMAP account has a fairly big hierarchy with many top and sublevel folders. 2. I open to mail window, login to default (IMAP/nsmail-2) account then login to both webmail accounts. I do not expand, select or otherwise access or login with the other accounts. 3. I go offline via File|Offline|Download/Sync now, but choose Don't Download and no send unsent messages, I do go offline after sync. I do have one webmail inbox selected for offline, but again, I don't download when going offline. 4. The webmail accounts are 2nd and 4th account in the folder pane. 5. With the default/1st IMAP account still expanded, in offline state I select a subfolder in one of the webmail accounts, collapse/expand/collapse its parent. Then I collapse the webmail account and expand again. In many cases this will cause the folder pane to mysteriously scroll back to the top, where the default account INBOX is. 6. At this point I move my mouse over from folder pane to thread pane area and a crash occurs. Will attach from talkback report(s). Incidents: 30586628,30586507,30586439,30586359
Attached file incident 30586628 (deleted) —
Now that I look at the talkback reports, it looks a lot like trace from 81273...will let you guys take a look and duplicate if so.
QA Contact: esther → laurel
yes, you're right, Laurel, that stack trace looks exactly the same. Also, I can't reproduce this problem with my debug build from today which has the fix for bug 81273 *** This bug has been marked as a duplicate of 81273 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Marking verified as a duplicate.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: