Created attachment 656799 [details] 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
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.
Severity: normal → critical
Crash Signature: [@ pr_FindSymbolInLib]
Component: Untriaged → Plug-ins
Product: Firefox → Core
Hardware: x86_64 → x86
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.
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?
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.
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.
Is this still an issue in FF 24 release and java 7u40 ?
at least my win7 ff24 survives with a disabled java 188.8.131.52
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
also when setting "Ask to activate", it survives (10.17.2.2.)
You need to log in before you can comment on or make changes to this bug.