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

64-bit random JVM Crash on Win 2k3 server with 8G RAM

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.0u11
    • Fix Version/s: None
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • CPU:
      x86
    • OS:
      windows_2003

      Description

      ISV has reported Java crashing with the 64-bit Server VM on Windows 2003. This is reproducible on jdk1.5.0_06, jdk1.5.0_10, jdk1.5.0_11 and 1.6.0-b105 and happens on various different applications, but particularly JBoss Application Server. Each crash produces a hs_err log file but the stack trace is missing from each. The crash only occurs when the system has 8GB RAM installed and goes away when 4GB of RAM is removed, with these tests the Java command line is *not* changed. The test system is running intel em64t processors (not sure how many but will find out). Analysis of the hs_err logs suggests that the crash happens randomly although more often in the CMS collector. We have a crash dump from jdk1.5.0_11 and the stack trace from that shows the following:

      This dump file has an exception of interest stored in it.
      The stored exception information can be accessed via .ecxr.
      ntdll!DbgBreakPoint:
      00000000`78ef3320 cc int 3
      0:005> k
      Child-SP RetAddr Call Site
      00000000`05c7e8d8 00000000`083a8a59 ntdll!DbgBreakPoint
      00000000`05c7e8e0 00000000`083a814f jvm!VMError::show_message_box+0x99
      00000000`05c7e920 00000000`082e7d37 jvm!VMError::report_and_die+0x12f
      00000000`05c7e9b0 00000000`082e82af jvm!topLevelExceptionFilter+0x457
      00000000`05c7eb30 00000000`78ee6d43 jvm!os::init_2+0x43f
      00000000`05c7eb60 00000000`78ee4bdd ntdll!_C_specific_handler+0x9b
      00000000`05c7ebf0 00000000`78ee685a ntdll!RtlpExecuteHandlerForException+0xd
      00000000`05c7ec20 00000000`78ef3a5d ntdll!RtlDispatchException+0x1b4
      00000000`05c7f2d0 00000000`082b88a1 ntdll!KiUserExceptionDispatch+0x2d
      00000000`05c7f870 00000000`08314eb8 jvm!MarkSweep::FollowStackClosure::do_void+0x21
      00000000`05c7f8a0 00000000`08315295 jvm!PSMarkSweep::mark_sweep_phase1+0x98
      00000000`05c7f920 00000000`083159bb jvm!PSMarkSweep::invoke_no_policy+0x2d5
      00000000`05c7fb80 00000000`083ae1dd jvm!PSMarkSweep::invoke+0x6b
      00000000`05c7fbb0 00000000`083ae738 jvm!VM_ParallelGCSystemGC::doit+0xad
      00000000`05c7fbf0 00000000`083ad3f5 jvm!VM_Operation::evaluate+0x48
      00000000`05c7fc20 00000000`083ad922 jvm!VMThread::loop+0x305
      00000000`05c7fcd0 00000000`082e8256 jvm!VMThread::run+0x72
      00000000`05c7fd00 000007ff`7fc411c4 jvm!os::init_2+0x3e6
      00000000`05c7ff50 00000000`77d6b69a msvcrt!endthreadex+0xd4
      00000000`05c7ff80 00000000`00000000 kernel32!BaseThreadStart+0x3a

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              duke J. Duke (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: