Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4966481

JVM crash during presentation of a java.awt.FileDialog()



    • Type: Bug
    • Status: Closed
    • Priority: P2
    • Resolution: Won't Fix
    • Affects Version/s: 1.3.1_09
    • Fix Version/s: None
    • Component/s: hotspot
    • Subcomponent:
    • CPU:
    • OS:


      logs.txt content:
      Unexpected Signal : unknown exception code occurred at PC=0x77E73887
      Function name=RaiseException

      Current Java thread:
              at sun.awt.windows.WToolkit.eventLoop(Native Method)
              at sun.awt.windows.WToolkit.run(WToolkit.java:183)
              at java.lang.Thread.run(Thread.java:479)

      Dynamic libraries:
      0x00400000 - 0x00405000 D:\TGM\jre\bin\java.exe
      0x77F50000 - 0x77FF7000 C:\WINDOWS\System32\ntdll.dll
      0x77E60000 - 0x77F46000 C:\WINDOWS\system32\kernel32.dll
      0x77DD0000 - 0x77E5D000 C:\WINDOWS\system32\ADVAPI32.dll
      0x78000000 - 0x78086000 C:\WINDOWS\system32\RPCRT4.dll
      0x77C10000 - 0x77C63000 C:\WINDOWS\system32\MSVCRT.dll
      0x08000000 - 0x080D7000 D:\TGM\jre\bin\hotspot\jvm.dll
      0x77D40000 - 0x77DCC000 C:\WINDOWS\system32\USER32.dll
      0x77C70000 - 0x77CB0000 C:\WINDOWS\system32\GDI32.dll
      0x76B40000 - 0x76B6C000 C:\WINDOWS\System32\WINMM.dll
      0x10000000 - 0x10007000 D:\TGM\jre\bin\hpi.dll
      0x6D3B0000 - 0x6D3BD000 D:\TGM\jre\bin\verify.dll
      0x6D250000 - 0x6D268000 D:\TGM\jre\bin\java.dll
      0x6D3C0000 - 0x6D3CD000 D:\TGM\jre\bin\zip.dll
      0x6D020000 - 0x6D12B000 D:\TGM\jre\bin\awt.dll
      0x73000000 - 0x73023000 C:\WINDOWS\System32\WINSPOOL.DRV
      0x76390000 - 0x763AC000 C:\WINDOWS\System32\IMM32.dll
      0x771B0000 - 0x772D1000 C:\WINDOWS\system32\ole32.dll
      0x5AD70000 - 0x5ADA4000 C:\WINDOWS\System32\uxtheme.dll
      0x6D1E0000 - 0x6D21B000 D:\TGM\jre\bin\fontmanager.dll
      0x51000000 - 0x5104D000 C:\WINDOWS\System32\DDRAW.dll
      0x73BC0000 - 0x73BC6000 C:\WINDOWS\System32\DCIMAN32.dll
      0x06640000 - 0x06928000 C:\WINDOWS\System32\MTXOGL.DLL
      0x77C00000 - 0x77C07000 C:\WINDOWS\system32\VERSION.dll
      0x74720000 - 0x74764000 C:\WINDOWS\System32\MSCTF.dll
      0x773D0000 - 0x77BC2000 C:\WINDOWS\system32\SHELL32.DLL
      0x70A70000 - 0x70AD5000 C:\WINDOWS\system32\SHLWAPI.dll
      0x71950000 - 0x71A34000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.10.0_x-ww_f7fb5805\comctl32.dll
      0x77340000 - 0x773CB000 C:\WINDOWS\system32\comctl32.dll
      0x763B0000 - 0x763F5000 C:\WINDOWS\system32\COMDLG32.DLL
      0x75F40000 - 0x75F5F000 C:\WINDOWS\system32\appHelp.dll
      0x76FD0000 - 0x77048000 C:\WINDOWS\System32\CLBCATQ.DLL
      0x77120000 - 0x771AB000 C:\WINDOWS\system32\OLEAUT32.dll
      0x77050000 - 0x77115000 C:\WINDOWS\System32\COMRes.dll
      0x76620000 - 0x7666E000 C:\WINDOWS\System32\cscui.dll
      0x76600000 - 0x7661B000 C:\WINDOWS\System32\CSCDLL.dll
      0x75F80000 - 0x7607C000 C:\WINDOWS\System32\browseui.dll
      0x76670000 - 0x76757000 C:\WINDOWS\System32\SETUPAPI.dll
      0x75A70000 - 0x75B15000 C:\WINDOWS\system32\USERENV.dll
      0x76990000 - 0x769B4000 C:\WINDOWS\System32\ntshrui.dll
      0x76B20000 - 0x76B35000 C:\WINDOWS\System32\ATL.DLL
      0x71C20000 - 0x71C6E000 C:\WINDOWS\System32\NETAPI32.dll
      0x71700000 - 0x71849000 C:\WINDOWS\System32\shdocvw.dll
      0x1C000000 - 0x1C006000 C:\Program Files\AIM95\idlemon.dll
      0x71B20000 - 0x71B31000 C:\WINDOWS\system32\MPR.dll
      0x23400000 - 0x2340B000 C:\Program Files\Rational\ClearCase\bin\ccasenp.dll
      0x75F60000 - 0x75F66000 C:\WINDOWS\System32\drprov.dll
      0x71C10000 - 0x71C1D000 C:\WINDOWS\System32\ntlanman.dll
      0x71CD0000 - 0x71CE6000 C:\WINDOWS\System32\NETUI0.dll
      0x71C90000 - 0x71CCC000 C:\WINDOWS\System32\NETUI1.dll
      0x71C80000 - 0x71C86000 C:\WINDOWS\System32\NETRAP.dll
      0x71BF0000 - 0x71C01000 C:\WINDOWS\System32\SAMLIB.dll
      0x75F70000 - 0x75F79000 C:\WINDOWS\System32\davclnt.dll
      0x76C90000 - 0x76CB2000 C:\WINDOWS\system32\imagehlp.dll
      0x6D510000 - 0x6D58D000 C:\WINDOWS\system32\DBGHELP.dll
      0x76BF0000 - 0x76BFB000 C:\WINDOWS\System32\PSAPI.DLL

      Local Time = Wed Nov 26 13:23:22 2003
      Elapsed Time = 1090
      # The exception above was detected in native code outside the VM
      # Java VM: Java HotSpot(TM) Client VM (1.3.1-internal mixed mode)
      # An error report file has been saved as hs_err_pid3716.log.
      # Please refer to the file for further information.

      The bug's attached zip file [826214-120803.zip] contains the following files:

      java.dmp - DMP captured after 1st exception
      java2.dmp - DMP captured after 2nd exception
      kurts.rtf - System control panel showing OS version
      logs.txt - thread traceback, loaded DLLs, and active threads
      TestFileOpen.bat - Test program
      TestFileOpen.class - Test program
      TestFileOpen.java - Test program
      crash.jpg - jpeg image showing where in happens w/ the FileDialog
      549023.zip - jvm debug files

      Some background: Cust haven't been able to catch a Dr Watson dump for this
      exception with the -XX:+ShowMessageBoxOnError java option: the JVM exits /
      crashes before it can cause the .dmp file to be produced. However, he was
      able to catch this exception on a PC which had Visual Studio installed, and
      he could do some basic debugging.

      The setup was as follows:

      * JVM 1.3.1_09 with some debug java DLL's and PDB's received for another
      problem ([825446] - the file 549023.zip -- this was a pre-release

      * WinXP, SP1.

      * The test program are in TestFileOpen.*. The hotspot occurs when the
      dropdown menu (circled in crash.jpg) in the FileDialog is clicked.

      * He collected data with Visual Studio 2002.

      After launching the JVM and test program, the cust. instrumented the process with
      visual studio, then touched the dropdown menu control. Then He caught TWO
      exceptions as shown in logs.txt in the 826214.zip file.

      * The first exception occurred in an unknown thread: logs.txt shows the
      traceback, the list of loaded modules, and the other threads in the process.
      After the 1st execption, he produced the java.dmp file to save the state of
      the process.

      * The second exception occurred immediately after he let the process resume
      normally from the 1st exception. The 2nd exception looks like it occurred in
      a JVM produced thread. Logs.txt shows the traceback and the list of other
      threads in the process. After this second exception, he produced the
      java2.dmp file to save the state of the process.

      After letting the process resume normally from the 2nd exception, he got the
      usual hotspot error traceback, appended to the end of logs.txt.




            ccheung Calvin Cheung
            duke J. Duke (Inactive)
            0 Vote for this issue
            0 Start watching this issue