United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6577944 Regression: handles and GDI objects leak in 6u4 b01
6577944 : Regression: handles and GDI objects leak in 6u4 b01

Details
Type:
Bug
Submit Date:
2007-07-07
Status:
Closed
Updated Date:
2013-01-10
Project Name:
JDK
Resolved Date:
2008-05-30
Component:
deploy
OS:
windows_xp,windows
Sub-Component:
plugin
CPU:
x86
Priority:
P4
Resolution:
Fixed
Affected Versions:
6u3,6u4
Fixed Versions:
6u10

Related Reports
Backport:
JDK-2152663 - Regression: handles and GDI objects leak in 6u4 b01
Backport:
JDK-2151177 - Regression: handles and GDI objects leak in 6u4 b01
Duplicate:
JDK-6586110 - Browser Hangs when Opening and closing ArcTest Demo.
Duplicate:
JDK-6586119 - Plugin leaks Memory, GDI Objects and Handle
Relates:
JDK-6550906 - IE/JVM crashes when modifying browser DOM from applet

Sub Tasks

Description
Handles and GDI objects leak was introduced in the JCG nightly build dated 5/31.
All JCG 6u3 nightly builds can be accessed from:
 http://javaweb.sfbay/jcg/NightlyBuilds/update.int/6u3/archived/

To reproduce - use a windows XP machine with IE browser:
- install JRE 6u3 build dated 5/31 or newer
- unzip the attached testcase (TC04-01.zip)
- load the TC04-01_Top.html into the browser
- set the interval to like 1s (1000)
- click on the launch button
- using taskmgr, you can observe that the handles and GDI objects counts are increasing

The leaked handles are mostly key (ZoneMap) see attached key-leak.txt.
The leaked GDI objects are mostly brushes.

Based on the following page, there was some java2d bug fixes for the 5/31 nightly build.
http://javaweb.sfbay/jcg/NightlyBuilds/update.int/6u3/archived/2007-05-31.6u3/changes

Comments
EVALUATION

This isn't reproducible with a recent 6u10 PIT build (b21) with the new plugin.
Attached is a iexplore.csv file showing both handles and GDI objects not increasing much during a 24-hour run. 
Since this has been fixed in the new plugin, I'm lowering this priority to p4.
2008-04-08 
EVALUATION

This is introduced by fix for 6550906. 
In that fix, we increased the ref count of the IDispatchWrapper COM object and 
ended up not releasing all of them.
A more correct fix is to not using smart point for the IDispatch COM object in 
ObjectTypeConverter::JobjectToVariant.
2007-07-18


Hardware and Software, Engineered to Work Together