[java] Crash when reloading page with many applets

RESOLVED INCOMPLETE

Status

--
critical
RESOLVED INCOMPLETE
10 years ago
3 years ago

People

(Reporter: mats, Unassigned)

Tracking

({crash, testcase})

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
Created attachment 363452 [details]
Testcase, zip archive

Spawned off from bug 336311 comment 5:

Downloaded zip, tried again in Firefox3.0.5 (Mozilla/5.0 (Windows; U; Windows
NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5)

Opened Firefox3, open, load page.  No flicker, acts better then IE(of course!) 
But, hit refresh and browser crashes.  Repeated experiment, crashed again.
(Reporter)

Comment 1

10 years ago
Created attachment 363453 [details]
stack for Java plugin's call to exit()

I can reproduce this in Firefox 2009021904 3.0.8pre on Linux (i686) with
Java(TM) Plug-in 1.6.0_07-b06.  The crash reporter does not trigger
though and I see the following messages on the console before it quits:

=============================
INTERNAL ERROR on Browser End: Could not register plugininstance

System error?:: Success
=============================

(fwiw, I have to reload the test.html page twice for it to happen)

It looks like the Java plugin decides to call exit() due to some
error it detects...  this is the call stack to exit().
(Reporter)

Comment 2

10 years ago
Devaun, please start Firefox and load about:crashes and copy-paste the
crash report ID to this bug, thanks.  See this URL for details:
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report

Updated

9 years ago
Component: Plug-ins → Java (Sun)
Product: Core → Plugins
QA Contact: plugins → sun-java

Comment 3

3 years ago
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

3 years ago
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.