JDK-7124401 : [macosx] After call Frame dispose() application continues to work
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Not an Issue
  • OS: os_x
  • CPU: generic
  • Submitted: 2011-12-23
  • Updated: 2012-07-16
  • Resolved: 2012-07-16
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.
http://java.net/jira/browse/MACOSX_PORT-243 submitted 2011/08/08 by Alexander Petrov
Build: b202
Keywords: test-fail-macos
Tests failed (Regression):
The test still failed on Mac OS X 10.7.4. with jdk 8 b39 even the fix integrated in b36.  I am not sure if that is due to that the test source code has not been updated as mentioned in Sergey's earlier comments.  The test source used is:
Please see the attached .jtr file for more information about how it failed.
Please make sure that the system on which test was executed, has correct Generic RGB Profile.

System preference -> Displays -> Color -> Generic RGB Profile

If it does not help please provide additional steps to reproduce.

EVALUATION On the latest version the dispose works as expected, but the test expects that the window will be fully red. But it is not true on the mac because of resizegrowboxwindow. Testcase updated.

SUGGESTED FIX http://cr.openjdk.java.net/~serb/7124401/webrev.00/

EVALUATION The test is actually not X11 specific, it just shows a frame with custom component inside and checks the visual appearance of this component. At the end it should call testFrame.dispose(), and I would indeed expect the test to exit, but something goes wrong... Raising it back to P3.

EVALUATION Author: Artem Ananiev Date: 14/Dec/11 03:33 PM Given the name of the failing test, I'd guess it's X11 specific, so lowering bug priority to 4 (Minor).