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

Java processes get killed, leaving no hs_err/stack trace on macOS 14.4

    XMLWordPrintable

Details

    • aarch64
    • os_x

    Description

      The test java/awt/color/MTICC_ColorSpaceToFrom.java became failing after updating macOS to 14.4 with exit code: 137
      The failure was detected on aarch64. The test successfully passes on x86-64. It is also successful on the previous versions of Sonoma

      Diagnostic report related to this failure looks like:

      ======================8<----------------------

      Process: java [4820]
      Path: /Users/USER/*/java
      Identifier: java
      Version: ???
      Code Type: ARM-64 (Native)
      Parent Process: java [4810]
      Responsible: Terminal [2470]
      User ID: 502

      Date/Time: 2024-03-11 23:36:05.6272 +0000
      OS Version: macOS 14.4 (23E214)
      Report Version: 12
      Anonymous UUID: 53991BD1-7C07-984F-8362-CC485246D2D9


      Time Awake Since Boot: 4100 seconds

      System Integrity Protection: enabled

      Crashed Thread: 34 Java: Thread-7825

      Exception Type: EXC_CRASH (SIGKILL)
      Exception Codes: 0x0000000000000000, 0x0000000000000000

      Termination Reason: Namespace GUARD, Code 5

      . . .

      Thread 34 Crashed:: Java: Thread-7825
      0 libjvm.dylib 0x1062d6ec0 _SafeFetchN_fault + 0
      1 libjvm.dylib 0x1062331a4 ObjectMonitor::TrySpin(JavaThread*) + 408
      2 libjvm.dylib 0x106232b44 ObjectMonitor::enter(JavaThread*) + 228
      3 libjvm.dylib 0x10637436c ObjectSynchronizer::enter(Handle, BasicLock*, JavaThread*) + 392
      4 libjvm.dylib 0x1062e6600 SharedRuntime::monitor_enter_helper(oopDesc*, BasicLock*, JavaThread*) + 156
      5 libjvm.dylib 0x1062e66c8 SharedRuntime::complete_monitor_locking_C(oopDesc*, BasicLock*, JavaThread*) + 76
      6 ??? 0x1164b5bb8 ???
      7 ??? 0x10454a8 ???

      . . .

      ======================8<----------------------

      See the attached java-2024-03-11-233605.ips

      No hotspot crash logs were generated for this failure.
      The failure was observed on 17, 21. Reproducibility: ~80%

      It could not be reproduced on 23-ea+13, 22+36-2370

      Attachments

        Issue Links

          There are no Sub-Tasks for this issue.

          Activity

            People

              dholmes David Holmes
              vprovodin Vitaly Provodin
              Votes:
              0 Vote for this issue
              Watchers:
              52 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: