288394 - java applet still running in background after closing the related tab in firefox

Status: RESOLVED INVALID

(Core Graveyard :: Plug-ins, defect)

Description

[BanX]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

after creating a java a applet running only the start() methods with an infinite
loop in it:
  while(true){
    int i = 0;
    i++;
  }

this applet will take 100% of cpu time.
after loading the applet in a new tab, firefox load it normally, but when
closing the related tab, surprisingly firefox doesnt kill the applet, and it
still running in background eating cpu time, and other resources.

Reproducible: Always

Steps to Reproduce:
1. create a java applet with an infinite loop in it
2. call this applet in a new tab (with other tabs open)
3. close the related tab, and remark that in task manager firefox still running
the applet by taking 100% of cpu time (+memory)

Actual Results:  
pc resources are taken by java applet after closing the related tab

Expected Results:  
when closing the applet's tab, firefox should kill the applet and stop running it

this is critical since if we consider an applet that enters a loop and stays in
it. a user who tryed to close it should restore it's pc resources back, but
instead the applet still running in background as if it haven't being closed.
the only way to restore resources back will be to close firefox with all other
tabs oppened.

Comment 1

[Daniel Veditz [:dveditz]]

I'm fairly sure there's another bug on problems shutting down Java...

Comment 2

[Daniel Veditz [:dveditz]]

I guess I can confirm this one in case we don't find the dupe. In any case we
don't need the security flag, this has been discussed in public before and we
also don't usually hide DOS bugs.

Comment 3

[Daniel Veditz [:dveditz]]

*** Bug 305056 has been marked as a duplicate of this bug. ***

Comment 4

[BanX]

(In reply to comment #2)
> I guess I can confirm this one in case we don't find the dupe. In any case we
> don't need the security flag, this has been discussed in public before and we
> also don't usually hide DOS bugs.

(In reply to comment #2)
> I guess I can confirm this one in case we don't find the dupe. In any case we
> don't need the security flag, this has been discussed in public before and we
> also don't usually hide DOS bugs.

Firefox 2.0 did not resolve this problem. After testing, this bug can be found on all firefox versions (1.*, 2.0).

Comment 5

[BanX]

The bug have not been resolved in the latest pre-release version of Firefox 3 (beta 3).

Comment 6

[Matthias Versen [:Matti]]

BanX: IS this still an Issue with the latest JRE and FF3.0.5 ?
The new JRE should use the new NPAPI plugin instead of Oji

Comment 7

[BanX]

@Mathias:
I confirm the bug presence in FF_3.0.6, as for the Java being used, I've tested on OpenJDK version "1.6.0_0" provided by the Ubuntu distribution.

Comment 8

[Matthias Versen [:Matti]]

Thanks for testing, it seems that the Java plugin ignores the quit message.
OpenJDK doesn't seem to be the SUN JRE. Does this openJDK comes with an npapi plugin ?

A normal npapi plugin should get a quit message and it's a bug in the plugin itself if the plugin ignores the quit message.

Comment 9

[BanX]

@Mathias
OpenJDK comes with an npapi plugin, IcedTea (the one I used for the test). https://launchpad.net/ubuntu/jaunty/+package/icedtea6-plugin

I also confirm now that Firefox 3.0.6 with the latest official SUN JRE is affected as well with this bug. (Tested on a Windows Machine)

Comment 10

[mmortal03]

This should be fixed.  I recently installed the latest plugin, Java SE 6 Update 12, and I no longer see this bug in Vista.  I had been experiencing it just a week
ago, and thought I had the latest plugin, but it doesn't look like I did.  For
those experiencing this bug, please install the latest Java plugin, and then
get back to us.

http://www.java.com/en/download/

This bug is also probably duplicate of Bug 156994.

Comment 11

[BanX]

I confirm that this bug persist for the latest version of Firefox (ver 3.0.10).
On the other hand, this same bug seems to be disappeared in the beta 3 of Firefox (ver 3.1b3).
Testing was done on an Ubuntu machine. 

For Windows machines, I can confirm the presence of the bug for Firefox ver 3.0.8 on Win XP with latest Java from Sun.

(In reply to comment #10)
> This should be fixed.  I recently installed the latest plugin, Java SE 6 Update
> 12, and I no longer see this bug in Vista.  I had been experiencing it just a
> week
> ago, and thought I had the latest plugin, but it doesn't look like I did.  For
> those experiencing this bug, please install the latest Java plugin, and then
> get back to us.
> 
> http://www.java.com/en/download/
> 
> This bug is also probably duplicate of Bug 156994.

Comment 12

[Mihai Morar, (:MihaiMorar)]

BanX can you please attach a testcase with an applet, so I can verify this issue on Latest Nightly and FF 19b1.

Comment 13

[Mihai Morar, (:MihaiMorar)]

(In reply to BanX from comment #0)

I tried to reproduce this using following steps.

1. Open Web Console (Ctrl+Shift+K)
2. Type this:   var x=true; var i=1; while(x){ i++; } - this is my infinite loop.

Actual results: FF Hangs for 1min and a dialog box is opened which said Unresponsive Script. You can choose Continue or Stop Script.

This is expected to do, so based on this I consider this issue Resolved Invalid.

Comment 14

[Mihai Morar, (:MihaiMorar)]

I got the results from Comment 13 on Windows 7 x64, ubuntu x86 and Mac OS 10.8

Builds: FF 19b5, Latest Nightly (2013-02-11) and FF 4.0

Comment 15

[Mihai Morar, (:MihaiMorar)]

Attachment: testcase

Testcase used in Comment 13