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

Section hang, java.EXE don't end after exit of GUI with System.exit on Win XP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P2 P2
    • None
    • 1.4.0
    • client-libs
    • x86
    • windows_xp

      This occurs on WinXP Prof. RC2 and WinXP Home RC2 Only.
      Win 98 2nd, ME, and 2000 prof are fine.
      Command Prompt Section hanging because java.EXE don't end after exit of GUI with System.exit

      This problem was found with Merlin-beta2 B77 can be tracked down to B73. B72 and before are Okay.

      A sample: FreezeTest.java can be found in the attachment.
      To reproduce the bug:
      1) Copy the file to say c:\FreezeTest.java
      2) Set JAVA_HOME=location of latest jdk (b77).
         eg set JAVA_HOME=c:\jdk1.4 in Cammand Prompt.
      3) At c:\ compile with $JAVA_HOME\bin\javac FreezeTest.java
      4) At c:\ run with $JAVA_HOME\bin\java FreezeTest
      5) Click on the button in applet.
      6) The applet exit but command prompt didn't return as it should.
      7) In addition, "Ctrl-Break" doesn't produce a stack dump before prompt return.
      8) if not using "Ctrl-Break", java.EXE can be found in Task Manager after applet exited. Command prompt will return after java.EXE been killed from Task Manager.

      Most of Swing BAT_Suite cases failed because of this bug such as BeanFire, KeyFire, and UIMape. Test results were verified with Edmund Lou.

            mmartaksunw Michael Martak (Inactive)
            duke J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: