JDK-6268999 : Regression: java/awt/FileDialog/FileDialogBufferOverflowTest/FileDialogBufferOverflowTest.html fails
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2005-05-11
  • Updated: 2011-01-19
  • Resolved: 2005-07-01
Related Reports
Relates :  
Description
		
JDK        	    : Mustang b35
Platform[s]         : Fails On:  win2000 Prof
Failing Test [s]    : java/awt/FileDialog/FileDialogBufferOverflowTest/FileDialogBufferOverflowTest.html


    Test source location:
    =====================
/java/re/jdk/6.0/latest/ws/j2se/test/java/awt/FileDialog/FileDialogBufferOverflowTest/FileDialogBufferOverflowTest.html

    jtr file location:
    ==================
/net/cady/export6/results/mustang/b35/reg/regression-reg-win2000-2005-05-06-16-17-24-0712/workDir/java/awt/FileDialog/FileDialogBufferOverflowTest/FileDialogBufferOverflowTest.jtr

    How to reproduce:
    ====================
    - Set JAVA_HOME to Mustang b35 windows-i586
    - map and cd /java/re/jdk/6.0/latest/ws/j2se/test/java/awt/FileDialog/FileDialogBufferOverflowTest 
    - /net/koori.sfbay/onestop/jct-tools/2.1.6/archive/fcs/binaries/win32/bin/jtreg -r:/tmp -w:/tmp FileDialogBufferOverflowTest.html

    Test output:
    =============
----------System.out:(15/529)----------
Any messages for the tester will display here.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x78379b40, pid=1948, tid=1652
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-ea-b35 mixed mode, sharing)
# Problematic frame:
# C  [SHELL32.DLL+0x89b40]
#
# An error report file with more information is saved as hs_err_pid1948.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
----------System.err:(17/1014)----------
java.lang.NullPointerException: null pData
        at sun.awt.windows.WComponentPeer.nativeHandleEvent(Native Method)
        at sun.awt.windows.WComponentPeer.handleEvent(WComponentPeer.java:273)
        at java.awt.Component.dispatchEventImpl(Component.java:4291)
        at java.awt.Container.dispatchEventImpl(Container.java:2025)
        at java.awt.Window.dispatchEventImpl(Window.java:1809)
        at java.awt.Component.dispatchEvent(Component.java:4049)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:591)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:247)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:168)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:154)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:115)
STATUS:Failed.Applet thread threw exception: java.lang.NullPointerException: null pData

This is the Motif-specific test case.

result: Failed. Unexpected exit from test [exit code: 1]


###@###.### 2005-05-11 21:48:51 GMT

Comments
EVALUATION The bug is filed against Mustang b35 build, but in b42 it is already not reproducible (confirmed by submitter, see comments section for details). There are some important fixes in windows native AWT code, it seems that one of them fixes this problem too. So I'm closing this bug as not reproducible. ###@###.### 2005-07-01 07:47:59 GMT
01-07-2005