JDK-8062053 : [macosx] huge native memory leak in AWTWindow.m
  • Type: Backport
  • Backport of: JDK-8041572
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 8,9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-10-24
  • Updated: 2014-11-27
  • Resolved: 2014-10-30
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 7 JDK 9
7u75 b07Fixed 9Fixed
Comments
Verified
27-11-2014
Note this fix must be back ported together with JDK-8041987, because this fix uncovered another bug in memory management. See comment in JDK-8041572.
30-10-2014
Critical Request Template: -Justification: it's a huge mem leak in native part, without fix every java application with UI based on AWT will leak on Mac platform. And the leak is very big that and appears on every mouse movement. -Risk Analysis: low risk -Webrev: http://cr.openjdk.java.net/~mcherkas/8051263/webrev.00/ -Testing: it can be easily tested manually: run SwingSet2, move cursor over the SwingSet2 window. Without the fix amount of consumed memory is growing fast, with the fix application's mem amount doesn't change. -Back ports (done/to-be-done) : all backports were done - FX Impact: no impact
29-10-2014
In progress flip
29-10-2014
There is a huge native memory leak in awt code on Mac OS X. This is regression introduced in JDK 7u66 and it looks identical to JDK-8041572. The leak can be easily reproduced using SwingSet2 with the following steps: 1) Run SwingSet2 demo on JDK 7u66 2) move mouse over the SwingSet2 window - for example make circles over the window The leak can be seen Activity Monitor and in details in vmmap output. The following output is captured, while moving mouse over SwingSet2 window. thurka$ jdk1.7.0_66.jdk/Contents/Home/bin/java -version java version "1.7.0_66" Java(TM) SE Runtime Environment (build 1.7.0_66-b17) Java HotSpot(TM) 64-Bit Server VM (build 24.66-b02, mixed mode) thurka$ jdk1.7.0_66.jdk/Contents/Home/bin/java -jar /Library/Java/Demos/JFC/SwingSet2/SwingSet2.jar & [1] 51865 thurka$ date; vmmap 51865 | grep ^DefaultMallocZone Fri Oct 24 13:01:17 CEST 2014 DefaultMallocZone_0x102308000 47.8M 70498 31.6M 65% thurka$ date; vmmap 51865 | grep ^DefaultMallocZone Fri Oct 24 13:01:32 CEST 2014 DefaultMallocZone_0x102308000 206.8M 3050186 186.2M 90% thurka$ date; vmmap 51865 | grep ^DefaultMallocZone Fri Oct 24 13:02:02 CEST 2014 DefaultMallocZone_0x102308000 696.8M 12200965 660.7M 94% thurka$ date; vmmap 51865 | grep ^DefaultMallocZone Fri Oct 24 13:02:34 CEST 2014 DefaultMallocZone_0x102308000 1.1G 20383965 1.1G 95% thurka$ As you can see DefaultMallocZone of SwingSet2 application raised to 1.1G in two minutes. Tom���� H��rka added a comment - 2014-10-24 04:38
24-10-2014