JDK-6480410 : Thread leak in applets
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2006-10-10
  • Updated: 2011-12-21
  • Resolved: 2007-08-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10Resolved 7Resolved
Related Reports
Duplicate :  
JDK-6399750 - RFE: Improve applet lifecycle and LiveConnect support in Java Plug-in
Relates :  
JDK-6526767 - Applet heap memory - OutOfMemoryError
Relates :  
JDK-6545649 - user thread leak in java plugin
Relates :  
JDK-6462598 - thread leaking in IE fast open and close of applet
Description
By repeatedly clicking the refresh button in IE I noticed a serious memory
leak. It appears in some cases (not all) doing so causes the plugin to
leak threads. The attached screen shot below shows the state of the plugin JVM
after leaving the applet page.

This is with 1.6 b99, Internet Explorer.

I'm filling against deployment for the initial evaluation, this may turn out to be a problem else where in the VM.
I've also attached a test case from Chris.
Comments
EVALUATION This is fixed under CR 6399750. Close it as a duplicate.
21-08-2007
EVALUATION This CR is tracking the applet handler thread leak issue. I log another CR 6545649 for aplet user thread leak. The applet handler thread leak is caused by out order of applet life cycle events. Since applet initialization is on a seperate thread (Initer), it is possibly that stop/destroy events are sent before the init/start. When an applet is not initialized, stop() and destroy() are basically no-op. Thus caused applet handler thread leak.
12-04-2007
EVALUATION There's is applet thread leakage if the applet is refreshed aggressively. This problem exists also in 5.0 update releases. To reproduce this: - enable java console - load the applet - refresh the applet - while the animation is going on, refresh the applet again. - priodically, press "t" at the console to monitor the java threads You'll see there're multiple applet thread (in this case thread applet-dummy.DummyApplet,4,alive) in the applet thread group such as the following at the java console: Group file:/F:/Bug6480410/applet_bug/dummy/-threadGroup,ac=4,agc=0,pri=4 thread applet-dummy.DummyApplet,4,alive TimerQueue,4,alive,daemon AWT-EventQueue-14,4,alive thread applet-dummy.DummyApplet,4,alive Done. We're planning to address this kind of applet refresh issue in the jplan 427 (Improve applet lifecycle and LiveConnect support in Java Plug-in) in jdk 7. We may also backport part of all of the code changes into previous update release such as 6ux.
13-10-2006