Closed
Bug 650948
Opened 13 years ago
Closed 13 years ago
Java process doesn't get unloaded after tab/window closing
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 501485
People
(Reporter: timshel, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 I am not sure if it is only Linux specific but if you load a webpage with a Java applet a Java process is started which uses in my case around 130 MB RAM. If you close the tab or window with the applet the process doesn't get close. If you reopen this tab again the Java process uses 160 MB RAM. I got a case today where Java has used 300 MB without any running java applet. This process doesn't get unloaded until Firefox is closed. Of course the RAM usage of Java is not a Firefox issue but Firefox should unload plugin processes if the according tabs/windows are closed. At least in case of Java because if you don't close FF that often like in case of a laptop or company pc this could have a huge impact on performance. Not to mention that most people will probably blame Firefox for eating up all their RAM even if it is only partly true in this case. Reproducible: Always Steps to Reproduce: 1.open a website with a java applet 2.close the tab 3.check your processes for java Actual Results: Java is still running after closing the tab. Expected Results: Java should be closed, at least after a short time.
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•