Closed Bug 20921 Opened 25 years ago Closed 25 years ago

Mail crashed when scrolling Subject pane

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: kinmoz, Assigned: alecf)

Details

I clicked on one of my mailboxes, then after all the subject lines loaded, I tried to scroll the subject pane by grabbing the Gfx scrollbar thumb. I crashed with: nsGenericElement::GetParent(nsIContent * & 0x00000000) line 721 + 24 bytes AnonymousElement::GetParent(const AnonymousElement * const 0x03506f3c, nsIContent * & 0x00000000) line 74 + 18 bytes nsCSSFrameConstructor::FindPrimaryFrameFor(nsCSSFrameConstructor * const 0x02d76590, nsIPresContext * 0x02da4760, nsIFrameManager * 0x02d763b0, nsIContent * 0x03506f3c, nsIFrame * * 0x0012f55c) line 8070 StyleSetImpl::FindPrimaryFrameFor(StyleSetImpl * const 0x02d76630, nsIPresContext * 0x02da4760, nsIFrameManager * 0x02d763b0, nsIContent * 0x03506f3c, nsIFrame * * 0x0012f55c) line 1057 FrameManager::GetPrimaryFrameFor(FrameManager * const 0x02d763b0, nsIContent * 0x03506f3c, nsIFrame * * 0x0012f55c) line 420 PresShell::GetPrimaryFrameFor(const PresShell * const 0x00d667b0, nsIContent * 0x03506f3c, nsIFrame * * 0x0012f55c) line 2301 + 32 bytes nsCSSFrameConstructor::ContentStatesChanged(nsCSSFrameConstructor * const 0x02d76590, nsIPresContext * 0x02da4760, nsIContent * 0x00000000, nsIContent * 0x03506f3c) line 7031 StyleSetImpl::ContentStatesChanged(StyleSetImpl * const 0x02d76630, nsIPresContext * 0x02da4760, nsIContent * 0x0322bf8c, nsIContent * 0x03506f3c) line 984 PresShell::ContentStatesChanged(PresShell * const 0x00d667b8, nsIDocument * 0x02e27e10, nsIContent * 0x0322bf8c, nsIContent * 0x03506f3c) line 2114 + 46 bytes nsXULDocument::ContentStatesChanged(nsXULDocument * const 0x02e27e10, nsIContent * 0x0322bf8c, nsIContent * 0x03506f3c) line 1281 nsEventStateManager::SetContentState(nsEventStateManager * const 0x031dad10, nsIContent * 0x0322bf8c, int 4) line 1914 nsEventStateManager::GenerateMouseEnterExit(nsIPresContext * 0x02da4760, nsGUIEvent * 0x0012fb5c) line 1103 nsEventStateManager::PreHandleEvent(nsEventStateManager * const 0x031dad10, nsIPresContext * 0x02da4760, nsGUIEvent * 0x0012fb5c, nsIFrame * 0x022c3de8, nsEventStatus * 0x0012fa68, nsIView * 0x03232310) line 186 PresShell::HandleEvent(PresShell * const 0x00d667b4, nsIView * 0x03232310, nsGUIEvent * 0x0012fb5c, nsEventStatus * 0x0012fa68) line 2492 + 43 bytes nsView::HandleEvent(nsView * const 0x03232310, nsGUIEvent * 0x0012fb5c, unsigned int 8, nsEventStatus * 0x0012fa68, int & 0) line 841 nsView::HandleEvent(nsView * const 0x0322ff90, nsGUIEvent * 0x0012fb5c, unsigned int 8, nsEventStatus * 0x0012fa68, int & 0) line 826 nsView::HandleEvent(nsView * const 0x02d751c0, nsGUIEvent * 0x0012fb5c, unsigned int 28, nsEventStatus * 0x0012fa68, int & 0) line 826 nsViewManager::DispatchEvent(nsViewManager * const 0x02d73bc0, nsGUIEvent * 0x0012fb5c, nsEventStatus * 0x0012fa68) line 1678 HandleEvent(nsGUIEvent * 0x0012fb5c) line 69 nsWindow::DispatchEvent(nsWindow * const 0x02d744e4, nsGUIEvent * 0x0012fb5c, nsEventStatus & nsEventStatus_eIgnore) line 421 + 10 bytes nsWindow::DispatchWindowEvent(nsGUIEvent * 0x0012fb5c) line 442 nsWindow::DispatchMouseEvent(unsigned int 300, nsPoint * 0x00000000) line 3338 + 21 bytes ChildWindow::DispatchMouseEvent(unsigned int 300, nsPoint * 0x00000000) line 3556 nsWindow::ProcessMessage(unsigned int 512, unsigned int 0, long 20775847, long * 0x0012fdc8) line 2620 + 24 bytes nsWindow::WindowProc(HWND__ * 0x03cb050c, unsigned int 512, unsigned int 0, long 20775847) line 608 + 27 bytes USER32! 77e71250() MakeStringArray(unsigned int, char *) line 107 + 2 bytes
Assignee: phil → alecf
This is mine. Might be a dupe of bug 20508, but I have to investigate more. Kin, did you do anything like expand & collapse a thread?
No, I just clicked on one of my mailboxes, waited for it to load and then tried to scroll the subject pane to look for the message I wanted. I believe my mailboxes are sorted by date ... not sure if that matters.
Status: NEW → ASSIGNED
ok, then it's probably different. Thanks for the info. Sorting shouldn't matter, but still useful information.
QA Contact: lchiang → nbaca
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I actually haven't seen this since yesterday's XUL instability. I'm marking worksforme for now.
Kin, can you try with the latest build? I have been unable to reproduce the crash on my NT4 system using the commercial or the mozilla build on 12/6.
I'm unable to reproduce this in the 12/09/1999 commercial build.
yeah, I've noticed it's alot stabler - I think the original crash might just have been general XUL instability that day.
Status: RESOLVED → VERIFIED
ok, will mark verified based on last few comments.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.