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

Java application crash

XMLWordPrintable

      FULL PRODUCT VERSION :
      java version "1.8.0_40"
      Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
      Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)

      ADDITIONAL OS VERSION INFORMATION :
      Microsoft Windows [Version 6.1.7601]

      A DESCRIPTION OF THE PROBLEM :
      Application crash.
      We have a multithread application that works with sockets.
      After the application starts, and following some steps, the application crashes. A popup is shown in Windows with basic crash information. At this point, any profiler that was attached, could not read any more information about the application. The jstack command isn't working. The only thing that we can do now, is a memory dump from windows task manager. We can provide you this memory dump for further investigation.
      This problem only occurs on java 8. We tried different versions: update 30, 40 and 45.
      This problem doesn't occurs using java 7, update 71.
      This problem only occurs on windows. We tried on MAC OX, and Linux and the problems doesn't occurs.
      This problem occurs even if we compile the code with java 7 or java 8.

      When the application crashes:
      The application logging stops.
      The jvm doesn't log any error.

      There are 2 errors that windows is showing:
      **********
      Problem signature:
      Problem Event Name: APPCRASH
      Application Name: javaw.exe
      Application Version: 8.0.40.26
      Application Timestamp: 54fb753d
      Fault Module Name: StackHash_f746
      Fault Module Version: 0.0.0.0
      Fault Module Timestamp: 00000000
      Exception Code: c000041d
      Exception Offset: 0000000300000002
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
      Additional Information 1: f746
      Additional Information 2: f74614d496e6c9bc68cedcf669dc3289
      Additional Information 3: b06b
      Additional Information 4: b06b963fab04236948480ad2fffe59e2

      and

      Problem signature:
      Problem Event Name: BEX64
      Application Name: java.exe
      Application Version: 8.0.40.26
      Application Timestamp: 54fb753d
      Fault Module Name: StackHash_ddac
      Fault Module Version: 0.0.0.0
      Fault Module Timestamp: 00000000
      Exception Offset: 0000000300000002
      Exception Code: c0000005
      Exception Data: 0000000000000008
      OS Version: 6.1.7601.2.1.0.256.48
      Locale ID: 1033
      Additional Information 1: ddac
      Additional Information 2: ddac38d5f825bba1b7ba9adcaecf7329
      Additional Information 3: 5df7
      Additional Information 4: 5df74ed5f023e0530c700a1143284825
      ********************

      REGRESSION. Last worked in version 7u80

      ADDITIONAL REGRESSION INFORMATION:
      java version "1.7.0_71"
      Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
      Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode)

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      We couldn't isolate a test scenario for you to reproduce. The problems occurs, when swing thread is involved, to paint a dialog, and another request of paint is trigger. The socket and other threads, are also running at this moment.
      For me it looks like a swing race condition that crashes the application.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      Application doesn't crash.
      ACTUAL -
      Application crashes, and Windows show a popup that application is not responding.

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      The hs_err_pid is not created.
      We can provide you the memory dump of the process for further investigation.

      REPRODUCIBILITY :
      This bug can be reproduced often.

      ---------- BEGIN SOURCE ----------
      We couldn't isolate a test case.
      ---------- END SOURCE ----------

      CUSTOMER SUBMITTED WORKAROUND :
      Couldn't find one.

      SUPPORT :
      YES

            pardesha Pardeep Sharma
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: