Closed Bug 94443 Opened 24 years ago Closed 23 years ago

Crashes if I open notebooks section and click on roughly 3 links

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 98
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 68488

People

(Reporter: js, Assigned: jst)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3+) Gecko/20010807 BuildID: 2001080703 While looking at Dell notebooks, the browser would commit a fatal error and crash. It didn't seem to depend on which page I was at, only that I had been to roughly 3-6 pages before that. I reproduced this bug 3 times. Reproducible: Sometimes Steps to Reproduce: 1.go to www.dell4me.com 2.Open notebooks category 3.Select the Inspiron 2500, cheapest edition 4.Fool around with the customizing tabs 3-6 times 5. Actual Results: It crashed with a fatal exception
John, can you please use a talkback build (the 0.9.3 build you have should work, email me if you need a hand) and try this. Please post the talkback id here and I can get it pulled. Thanks Zach
I crashed twice, build 2001-08-08-04 on Windows 98 SE. (However, Talkback could not connect to the server.)
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash
talkback servers seem to be back, can you try again?
Was able to repeat it, build 2001-08-09-04 on Win98. Talkback succeeded this time.
Mats: can you post the talkback id number here, it should appear somewhere in the talkback window and we need it to know what is going on. Thanks
Sorry but there was no number (I intentionally looked for it but there was none) In the comments field I wrote "Bugzilla bug 94443", I also filled in the email field. It was sent just a few minutes before my last comment. Hope this helps...
Oops, I did it again :) (I looked very carefully in the dialogs presented and I am positive - there was no Talkback id. Build 2001-08-09-04 on Windows 98 SE, I downloaded "mozilla-win32-talkback.zip" and unzipped it.)
mats, after you send in the report go to your install directory/components/talkback.exe and run the talkback program. If you install a new build the old IDs will be lost so do it immediately after you send in the report.
Thanks Asa, I found the Talkback IDs: TB33983500G TB33978459X
FWIW: First id is: GlobalWindowImpl::DropTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3561] nsGlobalWindow_RunTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3703] nsTimer::Fire [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimer.cpp, line 196] nsTimerManager::FireNextReadyTimer GlobalWindowImpl::DropTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3561] nsGlobalWindow_RunTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3703] nsTimer::Fire [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimer.cpp, line 196] nsTimerManager::FireNextReadyTimer [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimerManager.cpp, line 117] nsAppShell::Run [d:\builds\seamonkey\mozilla\widget\src\windows\nsAppShell.cpp, line 118] nsAppShellService::Run [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 425] main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1297] main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1602] WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1620] WinMainCRTStartup() KERNEL32.DLL + 0x1b560 (0xbff8b560) KERNEL32.DLL + 0x1b412 (0xbff8b412) KERNEL32.DLL + 0x19dd5 (0xbff89dd5) 0xc4fe4300 0x11000000 [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimerManager.cpp, line 117] FireTimeout [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimer.cpp, line 91] KERNEL32.DLL + 0x2317 (0xbff72317) FireTimeout [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimer.cpp, line 51] USER32.DLL + 0x3bb5 (0xbff53bb5) 0x2fd40003 0x8bf2468b The second one is: GlobalWindowImpl::DropTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3561] nsGlobalWindow_RunTimeout [d:\builds\seamonkey\mozilla\dom\src\base\nsGlobalWindow.cpp, line 3703] nsTimer::Fire [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimer.cpp, line 196] nsTimerManager::FireNextReadyTimer [d:\builds\seamonkey\mozilla\widget\timer\src\windows\nsTimerManager.cpp, line 117] nsAppShell::Run [d:\builds\seamonkey\mozilla\widget\src\windows\nsAppShell.cpp, line 118] nsAppShellService::Run [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 425] main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1297] main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1602] WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1620] WinMainCRTStartup() KERNEL32.DLL + 0x1b560 (0xbff8b560) KERNEL32.DLL + 0x1b412 (0xbff8b412) KERNEL32.DLL + 0x19dd5 (0xbff89dd5) 0xc4fe4300 0x11000000
->jst. Probably duplicate of bug 68488. It would be nice to see this fixed on the trunk as well.
Assignee: asa → jst
Component: Browser-General → DOM Level 0
QA Contact: doronr → desale
*** This bug has been marked as a duplicate of 68488 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified Duplicate
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.