162604 - Opening two or three news stories as new tabs crashes Mozilla

Status: RESOLVED DUPLICATE of bug 146027

(SeaMonkey :: General, defect)

Description

[samlew_lksk]

The url points to a local Toronto news web site. The content changes daily and
will have changed by about Friday morning 4AM EDT.

I haven't had any problems with that web site for the past week until today, so
it's likely once the content changes, the circumstances that cause the crash may
have disappeared. However, I've tried that web page five times today and Mozilla
crashed each time.

FWIW, I opened the web page, then opened the "Boy 12, loses fingers" news story
using the right mouse button "open link in new tab", then the "Another reason to
sleep in" story in a new tab, then "The Hawk still smiling" story. On the first
four crashes, Mozilla crashed after the second or third story was opened, after
a delay of a few seconds. The fifth crash, which occurred while making sure the
bug was still there while writing up this bug report, was different, the crash
didn't occur until I closed down one of the tabbed windows.

On the previous four crashes I allowed the Netscape bug report manager to send
in the crash data.

Comment 1

[Matthias Versen [:Matti]]

Always include the buidl ID in a bug report.
Can you provide a talkback ID ?
(After talkback submitted the crash run mozilla/components/talkback to get the ID)

Comment 2

[samlew_lksk]

Sorry, I forgot to add the build ID, this was my first bug report.

The Build ID is 2002072104.

I checked that web site today, the problem seems to have shifted. I can open
several tabbed windows but today Mozilla crashed when I had closed all the windows.

What is a talkback ID?

Comment 3

[Matthias Versen [:Matti]]

You can/should use a talkback enabled build.
Talkback detects the crash and send the informations to a netscape server.
(You get a window where do you can enter additional informations, comments and
your email adress)
We (or better Netscape people only for privacy&security reasons) can extract the
informations and get a stack trace which shows where your mozilla crashed in the
code.

Comment 4

[samlew_lksk]

The Talkback Incident ID was TB9316732Y. I remember sending in two or three
incident reports, I'm not sure why there was only one Incident ID logged.

Anyway, sorry about that, I missed the last line of your first reply.

Comment 5

[samlew_lksk]

I checked that web page and the Mozilla crashes are occurring again today,
although  it seems they occur when I close down a tabbed window instead of
occurring a few seconds after opening the tabbed window.

The Talkback IDs for the crashes this morning are 

TB9383177M 10:42am EDT

TB9382877E 10:35am EDT

Comment 6

[samlew_lksk]

I did an experiment yesterday. I opened up the that url, the Canoe news web
page, in IE, Netscape 4.75 and Mozilla Build 2002072104.

IE was stable for hours and never crashed. Netscape 4.75 crashed by itself after
a fair amount of time, I would guess at least a few minutes. Mozilla was stable
but crashed as soon as I closed the web page.
Hope this helps.

Comment 7

[Andrew Schultz]

are you closing Mozilla or just the window with the web page?  If you crash
closing Mozilla, it's probably bug 162526 (and the original report is WFM,
right?).  That bug has been fixed, so you might try a newer build.

Comment 8

[samlew_lksk]

Mozilla crashes when I close just the tabbed window. It's also crashed a few
seconds after I open the second or third window. So far, it's just been that
Canoe news web page.

I think it might have something to do with the banner ad that the pages runs at
the top. It appears in the first window, but not in the subsequentn windows. But
I don't know if the ad isn't appearing because it triggers the crash, or if the
crash occurs before Mozilla has a chance to download the ad graphic.

Comment 9

[samlew_lksk]

I just upgraded to Mozilla 1.1 and went to the offending Canoe web site. The
problem wasn't fixed with 1.1, I just managed to crash MZ again. I opened up
four news stories as tabbed windows and MZ crashed just after I closed two of
the tabbed windows. The Talkback ID and details of the current crash are
TB10060443Y, 8/29/02, 4:44pm, Program Crash.

Comment 10

[greer]

nsImageBoxListener::OnStopDecode is covered in bug 146027 (a spinoff of bug 153815).

Marking DUPE of 146027.

Incident #10060443
--------------------
nsImageBoxListener::OnStopDecode
[c:/builds/seamonkey/mozilla/layout/xul/base/src/nsImageBoxFrame.cpp, line 876]
imgRequestProxy::FrameChanged
[c:/builds/seamonkey/mozilla/modules/libpr0n/src/imgRequestProxy.cpp, line 295]
imgRequest::FrameChanged
[c:/builds/seamonkey/mozilla/modules/libpr0n/src/imgRequest.cpp, line 339]
imgContainer::Notify
[c:/builds/seamonkey/mozilla/modules/libpr0n/src/imgContainer.cpp, line 460]
nsTimerImpl::Fire [c:/builds/seamonkey/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 352]
nsTimerManager::FireNextIdleTimer
[c:/builds/seamonkey/mozilla/xpcom/threads/nsTimerImpl.cpp, line 588]
nsAppShell::Run [c:/builds/seamonkey/mozilla/widget/src/windows/nsAppShell.cpp,
line 156]
nsAppShellService::Run
[c:/builds/seamonkey/mozilla/xpfe/appshell/src/nsAppShellService.cpp, line 452]
main1 [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1534]
main [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1881]
WinMain [c:/builds/seamonkey/mozilla/xpfe/bootstrap/nsAppRunner.cpp, line 1899]
WinMainCRTStartup()
KERNEL32.dll + 0x1b9ea (0x77f1b9ea)

*** This bug has been marked as a duplicate of 146027 ***