JDK-7174713 : [macosx] OOMemory failure and apparently regression in 7u6 b12
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: os_x
  • CPU: x86
  • Submitted: 2012-06-06
  • Updated: 2012-06-26
  • Resolved: 2012-06-26
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
7u6Resolved
Related Reports
Duplicate :  
JDK-7174718 - [macosx] Regression in 7u6 b12: PopupFactory leaks DefaultFrames.
Relates :  
JDK-7175169 - [macosx] Regression test closed/java/awt/Frame/RemoveNotifyTest/RemoveNotifyTest.html restart gui
Description
Mac OS X 10.7.4 macmini4,1 and iMac

Run closed/java/awt/AppContext/ReclaimOnDisposeTest/ReclaimOnDisposeTest.java -- it pass for me in b11 several times however in b12 it runs much longer and fails consistently with 

ava.lang.OutOfMemoryError: Java heap space
----------System.err:(16/894)----------
java.lang.RuntimeException: test failed.
	at ReclaimOnDisposeTest.launchGC(ReclaimOnDisposeTest.java:142)
	at ReclaimOnDisposeTest.test(ReclaimOnDisposeTest.java:58)
	at ReclaimOnDisposeTest.init(ReclaimOnDisposeTest.java:48)
	at ReclaimOnDisposeTest.main(ReclaimOnDisposeTest.java:193)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at com.sun.javatest.regtest.MainWrapper$MainThread.run(MainWrapper.java:94)
	at java.lang.Thread.run(Thread.java:722)
Comments
EVALUATION Note that I've just fixed a leak caused by 7149062 (see 7174718). Please verify if this also fixes this bug.
22-06-2012
EVALUATION This issue may also be causing the failure of a test described in 7174718.
22-06-2012