-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0, 1.4.2_10, 5.0
-
beta
-
generic, x86
-
generic, windows_2000, windows_xp
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2127411 | 5.0u5 | Tal Moscovitz | P2 | Resolved | Fixed | b04 |
| JDK-2127243 | 1.4.2_12 | Tal Moscovitz | P2 | Resolved | Fixed | b01 |
The JDK's windows printing implementation is leaking GDI objects : 2 per job
seems typical but it's not a "per-job" leak.
Its observable in a process which creates and in some minimal way uses
one or more PrinterJobs as both a growth in native process size (not Java heap)
and in the windows task manager as a leak in GDI Objects (select the column
to view this).
A program as simple as this can demonstrate the problem:
import java.awt.print.*;
public class PT {
public static void main(String[] args) {
PrinterJob printerJob = PrinterJob.getPrinterJob();
for (int i=0;i<10000;i++) {
printerJob.defaultPage();
}
}
}
###@###.### 2005-04-14 21:14:29 GMT
seems typical but it's not a "per-job" leak.
Its observable in a process which creates and in some minimal way uses
one or more PrinterJobs as both a growth in native process size (not Java heap)
and in the windows task manager as a leak in GDI Objects (select the column
to view this).
A program as simple as this can demonstrate the problem:
import java.awt.print.*;
public class PT {
public static void main(String[] args) {
PrinterJob printerJob = PrinterJob.getPrinterJob();
for (int i=0;i<10000;i++) {
printerJob.defaultPage();
}
}
}
###@###.### 2005-04-14 21:14:29 GMT
- backported by
-
JDK-2127243 JDK windows printing implementation leaks GDI objects.
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Closed
-