JDK-6659113 : Resources(Mem usage, Handles and GDI) is increasing with many printjob
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-02-05
  • Updated: 2010-12-03
  • Resolved: 2009-02-17
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.
Other Other
1.3-poolResolved 1.4-poolResolved
Related Reports
Relates :  
JDK-6255588 - JDK windows printing implementation leaks GDI objects.
Relates :  
JDK-6804608 - GC doesn't release resources(Mem/handle/GDI) with -Xms in 1.4.2_19
Relates :  
JDK-6407901 - additional fix for 6255588 - "JDK windows printing implementation leaks GDI objects"
Description
When a user tries to invoke printjob, resources(Mem usage, Handles and GDI) is increasing.

CONGIGURATION : 
 OS : WindowsXP(SP2, Japanese/English)
 JRE : 1.4.2_16/5.0u14/6.0u4/7b24

REPRODUCE : 
1. Open "task manager" and add the rows, "Mem usage", "Handle count" and "GDI objects"
2. Compile the attached test program, PT3.java
3. Invoke "java PT3"
4. Please watch the resources in Task Manager

NOTE:
 The attached program tries to invoke printJobs 10,000 times.
 The output of printer should be set to a fixed file.
 1. Open "printers and faxes"  in Control panel
 2. Click the existing printer and opne the properties
 3. Click "ports" tab
 3. Click "Add port.." button
 4. Select(high-light) "Local Port" in Printer Ports window and 
    click "New Port.." button
 5. Enter a file name (with full path name to the file) as port name.
   ex. D:\resource-leak-problem\dummy
Comments
WORK AROUND attrib.setDialog(JobAttributes.DialogType.NATIVE); in place of: attrib.setDialog(JobAttributes.DialogType.NONE);
12-03-2008
EVALUATION Customer is I guess using attrib.setDialog(JobAttributes.DialogType.NONE); because of some background process and this is where GDI leak is. I have tried it with attrib.setDialog(JobAttributes.DialogType.NATIVE); it looks fine. *** (#1 of 1): [ UNSAVED ] ###@###.###
12-03-2008