Closed Bug 108560 Opened 24 years ago Closed 23 years ago

Crash accessing prodigy home pages - nsBoxFrame::Destroy

Categories

(Core :: Layout, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: lchiang, Assigned: eric)

Details

(Keywords: crash, Whiteboard: [nsSupport])

Attachments

(1 file)

Crash accessing prodigy home pages - nsBoxFrame::Destroy Starting around 10-22, we've been getting quite a few Talkback reports on crashes on Prodigy home pages: swbell.prodigy.net myhome.prodigy.net Users have the above URLs set as their startup home page and crash upon startup. I cannot reproduce this since I don't have a Prodigy account. Working with SusieW on some contacts at Prodigy to see if anything has changed on their end. This crash happens with Communicator 4.x, Netscape 6.x. I'm filing in Bugzilla since I assume Mozilla is affected. I'm hoping to get some Mozilla contributors to comment here. Otherwise, I can move this bug to Bugscape. Stack Trace : nsBoxFrame::Destroy [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsBoxFrame.cpp, line 1009] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 116] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 119] nsBoxFrame::Destroy [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsBoxFrame.cpp, line 1009] nsGfxScrollFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsGfxScrollFrame.cpp, line 446] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 116] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 119] ViewportFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsViewportFrame.cpp, line 142] FrameManager::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrameManager.cpp, line 457] PresShell::~PresShell [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 1494] PresShell::`scalar deleting destructor' nsTextInputListener::Release [d:\builds\seamonkey\mozilla\layout\html\forms\src\nsGfxTextControlFrame2.cpp, line 235] nsCOMPtr_base::~nsCOMPtr_base [d:\builds\seamonkey\mozilla\xpcom\base\nsCOMPtr.cpp, line 50] GlobalWindowImpl::Focus [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 1783] nsEventStateManager::PreHandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventStateManager.cpp, line 594] PresShell::HandleEventInternal [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5564] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5496] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 377] nsViewManager::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2056] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 68] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 724] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 741] nsWindow::DispatchFocus [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 4429] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3345] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 989] KERNEL32.DLL + 0x3613 (0xbff63613) KERNEL32.DLL + 0x248f7 (0xbff848f7)
Some Talkback IDs include: 37406928 37389603 Searching for "prodigy" in the user comments of Talkback will yield many matches.
Whiteboard: [nsSupport]
Severity: normal → major
Keywords: crash
Reassigning to Eric.
Assignee: attinasi → evaughan
I still have not been able to reproduce this crash using a Prodigy account created. I've asked our support team to find out the following: 1. Personalization on the myhome prodigy page so I can set up the same way Shiva - is this crash still prevalent in the top crash reports? Having a hard connecting to the talkback server at this time.
I am only seeing 7 comments refering to Prodigy in the last ten days of data (too few to be included in the comment reports). None of those is from the signature listed in the summary of the bug (nsBoxFrame::Destroy). I'll attach the signatures and comments in case you want to see them.
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: major → critical
-- This is pretty old bug. -- Verified on latest mozilla trunk and Netscape 7.0 with the home page set to swbell.prodigy.net myhome.prodigy.net I tried lot of times restarting the browser but could not reproduce. Looks like the problem is fixed. -- Marking it WORKSFORME.
Status: NEW → RESOLVED
Closed: 23 years ago
Priority: -- → P1
Resolution: --- → WORKSFORME
-- Marking Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: