JDK-4126442 : Memory leak running java app on solaris only.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: unknown,1.1
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 1998-04-07
  • Updated: 2022-10-21
  • Resolved: 1998-12-16
Related Reports
Duplicate :  
JDK-4116436 - StringIndexOutOfBoundsException with getSelectedText()
Description
We have found a memory leak on solaris when running a java application.The app
was developed using jbuilder on NT.When we run the app on solaris 2.6 we lose 
memory.We have run the app on NT ver 4 javastation and JavaPC with no mem leaks.I have also downloaded the JDK 1.1.3 1.1.4 1.1.5 1.1.6 and 1.2 beta with no change in status.
peter.castle@rsa 1998-04-24
Comments
PUBLIC COMMENTS Memory leak when running java app on solaris,IBM NC and Oracle NC but no mem leak on NT,javastation and JavaPC.
10-06-2004
EVALUATION I can reproduce this on Solaris. Running with the -Xhprof option to the 1.2beta4 VM, I see that the memory hogger is this stack trace: TRACE 2842: java/awt/image/DataBufferInt.<init>(DataBufferInt.java:44) java/awt/image/Raster.createPackedRaster(Raster.java:171) java/awt/image/DirectColorModel.createCompatibleWritableRaster (DirectColorModel.java:544) sun/awt/motif/MComponentPeer.createImage(MComponentPeer.java:225) ... rank self accum bytes objs bytes objs trace name 1 55.03% 55.03% 883440 20 883440 20 2842 [I Assigning to classes_awt because this is definitely a GUI problem. anand.palaniswamy@Eng 1998-04-14 This problem is still occuring with 1.1.7. Lara Bunni. robi.khan@eng 1998-07-31 The submitted fix is for 4116436. That fixes part of the problem, the rest is caused by the user's program code, which adds objects to a hashtable but doesn't remove them. matthew.chapman@eng 1998-09-29
29-09-1998
SUGGESTED FIX IBM has submitted a fix.Pleas find attachment. (motiffix.jar) peter.castle@rsa 1998-06-05 The submitted fix is for 4116436. That fixes part of the problem, the rest is caused by the user's program code, which adds objects to a hashtable but doesn't remove them. matthew.chapman@eng 1998-09-29
29-09-1998
WORK AROUND IBM have found a fix see Suggested Fix peter.castle@rsa 1998-06-05
05-06-1998