106209 - Browser crash - repeatable

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Kendes]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

Browser crash while visiting www.radiotimes.com

Reproducible: Always
Steps to Reproduce:
Go to www.radiotimes.com. Click on tonights TV link. Scroll times forward twice
to later shows (this may not be necessary). Clink on a link to show the details
for a particular show, one in the Channel/Times grid. A pop-up window will
appear - BANG!

Actual Results:  Erm, crashes. Dr Watson special.

Comment 1

[Kendes]

I am using Talkback, but it fails to send - I thnk because I'm behind a proxy
with  authentication switched on. Not sure how to get talkback to avoid this. I
can attach the exported text file from talkback if this helps (207k file).

Comment 2

[Adam Hauner]

Kendes, I tryed it with 2001102203-trunk/WinNT4 and coudn't repeat. Could you
try it with newer build? 

BTW attach talkback, it is useful...

Comment 3

[Ashley Bischoff (blog at handcoding.com)]

Kendes: You can get a more recent build here:
http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32-talkback.zip
(as always, be sure to delete your old Mozilla directory before installing the
new one)

Comment 4

[Matthias Versen [:Matti]]

wfm with win2k build 20011023..

Reporter: 
Please read http://www.mozilla.org/releases/mozilla0.9.5/
You can read there how you get talkback working with a proxy.
After talkback submitted the crash, run mozilla-dir\bin\componenets\talkback.exe
and poste the talkback ID.

Comment 5

[David Mason]

Just as an extra data point:  I was also experiencing this crash (under both
win32 and linux) using nightly builds dated about 10 days ago.

Updating to the latest nightly builds fixed the crashing for me.

Thanks.

Comment 6

[Ashley Bischoff (blog at handcoding.com)]

Marking WFM per comment ("Updating to the latest nightly builds fixed the
crashing for me"). Reporter: If this still occurs for you in today's build,
please reopen this bug.

Comment 7

[R.K.Aa.]

*** Bug 107218 has been marked as a duplicate of this bug. ***

Comment 8

[Kendes]

Just as a FYI -- updated build fixed the problem for me too. Thanks.