167690 - this morning on 9/10/02 Mozilla crashes (unexpectly quits) [@ eh_rest_world_r10]

Status: RESOLVED DUPLICATE of bug 154699

(Core Graveyard :: Java: OJI, defect)

Description

[Gerard Allwein]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.1) Gecko/20020826

this morning on 9/10/02 Mozilla crashes (unexpectly quits), I'm not sure if this
related to other bugs, nothing I saw directly relates to it. I'm unsure just
what on that page is causing the crash. If they change the page before someone
can check it, they might remove whatever is causing the crash.

Reproducible: Always

Steps to Reproduce:
1. go to http://news.bbc.co.uk/
2. watch it load
3. watch it unexpectly quit

Actual Results:  
Unexpectedly quit.

Expected Results:  
It shouldn't unexpectedly quit.

Comment 1

[Christopher Curzio]

Works for me, Linux - Build ID: 2002090922

Comment 2

[Greg K.]

WorksForMe using FizzillaCFM/2002090903 on 10.1.5.

That page contains a Java applet. Gerard, are you running Mac OS X 10.2? If so,
this is probably a dup of bug 154699. Please download a recent trunk nightly
that includes the fix for that bug and retest.

Comment 3

[Gerard Allwein]

I got last night's build, which [e-mail] thought might have
the bug fixed. 

The bug is still there. The version of the build is Mozilla 1.2a (seems like
there should be a more descriptive number somewhere but I couldn't find it).

Comment 4

[Greg K.]

Gerard, the build ID is displayed on browser window titlebars.

Please attach a crash report generated by this crash.

Comment 5

[Gerard Allwein]

Attachment: stack/register/thread dump of crash

[e-mail] also asked for the build id, sez it is in the title
bar. Well, it isn't on my title bar. I recall it used to be there several
builds back but lately it has only been showing the page title.

Comment 6

[Greg K.]

Gerald, for future reference, it's only necessary to attach one individual crash
report rather than the whole log, which in your case contains 6 individual reports.

Reassigning to OJI.

Comment 7

[Greg K.]

Gerard, how about the version? Is it 1.1?

Comment 8

[Gerard Allwein]

From Additional Comment # 3:

"I got last night's build, which [e-mail] thought might have
the bug fixed. 

"The bug is still there. The version of the build is Mozilla 1.2a (seems like
there should be a more descriptive number somewhere but I couldn't find it)."

Umm...I'm not sure how to get the actual build number because it isn't on the
title bar like it is supposed to be. Comment # 3 resulted from me picking up 
2002-08-11's nightly build and trying it. Hence it would have been the nightly
build of 1.2a.

Is there some way to force Mozilla to cough up it's build number if it doesn't
appear on the title bar?

I should mention, I have done quite a bit of development in the past. I'm not
averse to poking around in the innards of things. I don't know much about
Mozilla's innards, however.

Comment 9

[Joe Chou]

Mac bug, re-assign to Babak.

Comment 10

[MyBugzillaAcc]

I downloaded the nightly build 2002091014 and went to the page
http://news.bbc.co.uk/shared/hi/interstitial-news.stm.  The page loaded and the
browser did not quit.  I tested under Mac OS X 10.2.1.

Comment 11

[Greg K.]

Gerard, if you did actually download a nightly build, it would show a 10-digit
build ID on the window title bar. If you don't see the ID, you didn't download a
nightly build.

Comment 12

[Gerard Allwein]

"if you did actually download a nightly build, it would show a 10-digit
build ID on the window title bar. If you don't see the ID, you didn't download a
nightly build."

Respectfully, Greg, I did download the nightly build. My only guess is that it
was so close to 1.2a's release that it didn't have the build number on the
window title bar. I will, however, try last nights build now.

Comment 13

[Gerard Allwein]

Last night's build, 2002093010, does not exhibit this bug.

Comment 14

[Greg K.]

Resolving dup per comment 13. Gerard, if you encounter this problem again, feel
free to reopen this bug.

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

Comment 15

[Patty Mac]

Chris Petersen is a new QA contact for oji component. His email is:
[e-mail]

Comment 16

[Matthias Versen [:Matti]]

fixing small error for [e-mail] (filter with : SPAMMAILSUCKS)