JDK-6330322 : regression test java/awt/Dialog/DialogOverflowSizeTest/DialogSizeOverflowTest.html failed
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-09-29
  • Updated: 2011-03-07
  • Resolved: 2011-03-07
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
7 b04Fixed
Related Reports
Relates :  
Relates :  
Description
Tested environment:
Platform: Windows XP Professional SP2
locale: ja
JDK build: promoted Mustang b52

Following is the jtreg output. Also tested with latest jdk b53 and it resulted same.

#Test Results (version 2)
#Wed Sep 28 21:03:05 JST 2005
#checksum:2efcc315b9a58cfc
#-----testdescription-----
$file=E:\\java_sqa\\test\\java\\awt\\Dialog\\DialogOverflowSizeTest\\DialogSizeOverflowTest.html
$root=E:\\java_sqa\\test
author=###@###.###: area=awt.toplevel
keywords=bug4904961
run=USER_SPECIFIED applet DialogSizeOverflowTest.html\r\n
source=DialogSizeOverflowTest.html
title=Test that Dialog with zero sizes won't be created with negative sizes due to overflow in peer code

#-----environment-----

#-----testresult-----
description=file:///E:/java_sqa/test/java/awt/Dialog/DialogOverflowSizeTest/DialogSizeOverflowTest.html
end=Wed Sep 28 21:03:05 JST 2005
environment=regtest
execStatus=Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Test failed
javatestOS=Windows XP 5.1 (x86)
javatestVersion=2.1.5
script=com.sun.javatest.regtest.RegressionScript 
sections=script_messages build compile applet
start=Wed Sep 28 21:03:01 JST 2005
status=Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Test failed
test=java/awt/Dialog/DialogOverflowSizeTest/DialogSizeOverflowTest.html
work=E:\\java_sqa\\JTwork\\java\\awt\\Dialog\\DialogOverflowSizeTest

#section:script_messages
----------messages:(4/197)----------
JDK under test: (D:/jdk1.6.0)
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b52)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b52, mixed mode, sharing)

#section:build
----------messages:(3/111)----------
command: build DialogSizeOverflowTest 
reason: Named class compiled on demand
elapsed time (seconds): 2.062
result: Passed. Compilation successful

#section:compile
----------messages:(3/192)*----------
command: compile E:\\java_sqa\\test\\java\\awt\\Dialog\\DialogOverflowSizeTest\\DialogSizeOverflowTest.java 
reason: .class file out of date or does not exist
elapsed time (seconds): 2.062
----------System.out:(0/0)----------
----------System.err:(2/475)*----------
\u6ce8:E:\\java_sqa\\test\\java\\awt\\Dialog\\DialogOverflowSizeTest\\DialogSizeOverflowTest.java \u306f\u63a8\u5968\u3055\u308c\u306a\u3044 API \u3092\u4f7f\u7528\u307e\u305f\u306f\u30aa\u30fc\u30d0\u30fc\u30e9\u30a4\u30c9\u3057\u3066\u3044\u307e\u3059\u3002
\u6ce8:\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001-Xlint:deprecation \u30aa\u30d7\u30b7\u30e7\u30f3\u3092\u6307\u5b9a\u3057\u3066\u518d\u30b3\u30f3\u30d1\u30a4\u30eb\u3057\u3066\u304f\u3060\u3055\u3044\u3002
result: Passed. Compilation successful

#section:applet
----------messages:(3/148)----------
command: applet DialogSizeOverflowTest.html
reason: User specified action: run applet DialogSizeOverflowTest.html 
elapsed time (seconds): 2.188
----------System.out:(0/0)----------
----------System.err:(18/1219)----------
java.lang.RuntimeException: Test failed
	at DialogSizeOverflowTest$2.componentResized(DialogSizeOverflowTest.java:78)
	at java.awt.Component.processComponentEvent(Component.java:5752)
	at java.awt.Component.processEvent(Component.java:5706)
	at java.awt.Container.processEvent(Container.java:1960)
	at java.awt.Window.processEvent(Window.java:1561)
	at java.awt.Component.dispatchEventImpl(Component.java:4365)
	at java.awt.Container.dispatchEventImpl(Container.java:2018)
	at java.awt.Window.dispatchEventImpl(Window.java:2202)
	at java.awt.Component.dispatchEvent(Component.java:4195)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
STATUS:Failed.Applet thread threw exception: java.lang.RuntimeException: Test failed
result: Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Test failed


test result: Failed. Execution failed: Applet thread threw exception: java.lang.RuntimeException: Test failed

Comments
EVALUATION This test is for fix 4904961 and is specific to linux platform. On Windows we are attempting to construct a Dialog with less size then decorations are and expect that 100x100 is more then current size. Decorations adds extra pixels so it's real size is more. I carefully read 4904961 info and didn't find a mention for 100x100. Instead, near 65000 is meant. We may exclude this test on Windows or compare size with another values. This isn't related to a recent JDK6.0 fix 6323293. That was about RESIZED event dups but this is a bug in test.
19-10-2006

EVALUATION One of the possible ways is in changing the statement (!m_resizing) before sending an event. We used size comparison before and probably this is not a good way for now as the shared component should already has a new size so this check is not neccessary. As stated in header this variable (m_resizing) is used to track if we are in the middle of applying a new size. This seems done for preventing an extra resize event from sending while WM_EXITSIZEMOVE message doesn't come.
29-09-2005

EVALUATION its a regreession in JDK6.0b51. The test shows that componentResized Event comes to a Dialog dlg. *** (#1 of 1): [ UNSAVED ] ###@###.###
29-09-2005