264740 - Crash or freeze when closing a tab that is loading a Java powered website

Status: RESOLVED DUPLICATE of bug 98365

(Firefox :: General, defect)

Description

[Jean-Marc M.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

Firefox crashes or freezes when you close tab a that is loading a Java powered
website. I tried it two times on the DigiPosts website
(http://www.digiposts.com),  first time I closed the tab, Firefox closed it but
then it was kind of frozen, opening new tabs wouldn't load the website anymore
and when I tried to close Firefox, all tabs were closed, Firefox windows
disappeared from my Windows taskbar but there was still a Firefox process in the
task manager. And it never disappeared. I had to kill it. Second time Firefox
just crashed and I was able to send a bug report to the support by mail.

Java version : 1.4.2_05.

Reproducible: Always
Steps to Reproduce:
1. Open a new tab and visit the DigiPosts website (http://www.digiposts.com)
2. When you see that Firefox is launching the JRE (Jara Runtime Environment),
just try to close the tab
Actual Results:  
Freeze result : it seems Firefox successfully closed the tab but it's in fact
unstable, you can't properly visit websites in new tabs anymore for example.
Crash result : Firefox just crash and you can send a bug report by mail.

Expected Results:  
Firefox should stop launching the JRE as there's no more Java applet to run, and
go back to a stable state.

Comment 1

[Maria]

It happens always to me too, now also with Firefox/1.0RC2.

Comment 2

[Matija Polajnar]

With previous versions of Mozilla and Firefox I've had similar problems using
Adobe Reader 6.0 in a tab -- after closing the last tab with Reader in it,
Mozilla/Firefox began to behave strangly.

However, I have no problems now, with Firefox 1.0.
Closing a tab with http://www.digiposts.com "worksforme" (I'm writing this
comment in a browser in which I have just closed a tab with that page loaded).

Using Mozilla/5.0 (Windows; U; Windows NT 5.1; sl-SI; rv:1.7.5) Gecko/20041108
Firefox/1.0.

Comment 3

[Omry]

another related bug:
go to http://firefang.net/simulation/index.html
the applet shows.
try to refresh the page, and it wont load.
any new refresh seems to adds another applet thread:

Dump thread list ...
Group main,ac=20,agc=2,pri=10
    main,5,alive
    AWT-Windows,6,alive,dameon
    AWT-Shutdown,5,alive
    AWT-EventQueue-0,6,alive
    Thread-2092,5,alive
    Thread-2097,5,alive
    Thread-2102,5,alive
    Thread-2107,5,alive
Group Plugin Thread Group,ac=4,agc=0,pri=10
    Main Console Writer,6,alive
    AWT-EventQueue-1,6,alive
    Java2D Disposer,10,alive,dameon
    TimerQueue,5,alive,dameon
Group http://firefang.net/simulation/-threadGroup,ac=7,agc=0,pri=4
    thread applet-org.me4se.MIDletRunner,4,alive
    AWT-EventQueue-2,4,alive
    Thread-1962,4,alive
    Thread-2062,4,alive
    thread applet-org.me4se.MIDletRunner,4,alive
    thread applet-org.me4se.MIDletRunner,4,alive
    thread applet-org.me4se.MIDletRunner,4,alive
Done.


which means applets are not cleaned propertly when destroyed.
note : some applet may misbehave when destroyed, but they should still be
cleaned, forcefuly if needed.

Comment 4

[Richard Aspden]

I'm also getting this, with JRE 1.5.0_1. The behaviour appears to be specific to
closing a tab before the Java applet completely loads, leaving the JRE and
Firefox in a pseudo-hung state - clicking on other tabs doesn't update the
address bar, and it doesn't want to navigate anywhere.

I have also noted that while an applet is loading, switching tabs (via ctrl+tab
/ ctrl+shift+tab if it's relevant) will change the address bar once, then it
will be ignored for the rest of the tabs. I'm unsure if it's related.

Comment 5

[OstGote!]

see Bug 98365 too

Comment 6

[Tristor]

I am duping this to bug 98365, if anybody disagrees re-open.

*** This bug has been marked as a duplicate of 98365 ***

Comment 7

[Robin Monks]

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