786986 - crash when going to Java test page

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Ralf Hauser]

Attachment: addOns.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0
Build ID: 20120824154833

Steps to reproduce:

deactivate the java console as per the below screenshot,  go to 
http://www.heise.de/security/dienste/Java-403125.html 


Actual results:

firefox immediately disappeared both v15.0 and my pervious 14.x


Expected results:

it should tell me whether my browser is susceptible to the java 0-day or not as per http://www.heise.de/security/meldung/BSI-warnt-vor-hochkritischer-Java-Luecke-1677249.html

Comment 1

[Scoobidiver (away)]

Can you provide the crash ID from about:crashes? Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?

For your concern about the security, the Java Platform SE7u6 plugin and below will be blocklisted. See bug 785837.

Comment 2

[Ralf Hauser]

c0df81fe-9dfe-4975-a195-5cc4ea19f180  30.08.201212:33

Comment 3

[Ralf Hauser]

or https://crash-stats.mozilla.com/report/index/bp-5b5ef270-4bf9-48d7-9d8c-e59652120830

Comment 4

[Ralf Hauser]

correct, I copied the crash id of comment 2 via clipboard. Once I clicked on it, even though a sent date was already there, it started sending the crash and in the end the crash number and send date changed as per comment 3. Thereafter, clicking on the crash id again didn't redo the same suprising steps.

Comment 5

[Scoobidiver (away)]

Regarding comment 4, only 10% of crash reports are automatically submitted to Mozilla's servers to prevent their saturations. You need to click it to make it submit.

What about the safe mode?

Comment 6

[Robert Kaiser]

Does this also happen in 16 beta 1 (to be released today)? We fixed bug 700583 there, which has the same crash signature, so could be connected.

Comment 7

[:aceman]

I do see this on Win XP about twice a month:
bp-7edfa50b-3a34-4e50-b6b6-761392121012
bp-565d2f55-4ae9-4490-b587-1291a2121012
bp-1992415c-56a9-414b-9df0-c23582121012
bp-2e196747-2d07-4a20-a731-2c33a2121012
bp-770c9cda-7a32-4498-a2ec-ba41d2121012

Let's see if FF16 fixes it.

Comment 8

[Paul Silaghi, QA [:pauly]]

Is this still an issue in FF 24 release and java 7u40 ?

Comment 9

[Ralf Hauser]

at least my win7 ff24 survives with a disabled java 7.0.170.2

Comment 10

[Ralf Hauser]

also when setting "Ask to activate", it survives  (10.17.2.2.)

Comment 11

[Paul Silaghi, QA [:pauly]]

Thank you