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

Shenandoah: Test TestJcmdHeapDump.java#aggressive intermittent assert(gc_cause() == GCCause::_no_gc) failed: Over-writing cause

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3 P3
    • 25
    • 24
    • hotspot
    • gc
    • b07
    • aarch64
    • linux

        Test gc/shenandoah/TestJcmdHeapDump.java#aggressive intermittent assert(gc_cause() == GCCause::_no_gc) failed: Over-writing cause on linux-aarch64 by fastdebud build.

        The test log snippet:
        STDOUT:
        [2024-12-07T00:35:29.101488535Z] Gathering output for process 651326
        [2024-12-07T00:35:29.518459263Z] Waiting for completion for process 651326
        #
        # A fatal error has been detected by the Java Runtime Environment:
        #
        # Internal Error (src/hotspot/share/gc/shenandoah/shenandoahHeap.cpp:1516), pid=650235, tid=650303
        # assert(gc_cause() == GCCause::_no_gc) failed: Over-writing cause
        #
        # JRE version: OpenJDK Runtime Environment (25.0) (fastdebug build 25-internal-e0d63987)
        # Java VM: OpenJDK 64-Bit Server VM (fastdebug 25-internal-e0d63987, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, shenandoah gc, linux-aarch64)
        # Problematic frame:
        # V [libjvm.so+0x163aee0] ShenandoahHeap::on_cycle_start(GCCause::Cause, ShenandoahGeneration*)+0xfc
        #
        # Core dump will be written. Default location: /tmp/tone/run/jtreg/jt-work/jtreg/hotspot_jtreg/gc/shenandoah/TestJcmdHeapDump_aggressive/core.650235
        #
        # An error report file with more information is saved as:
        # /tmp/tone/run/jtreg/jt-work/jtreg/hotspot_jtreg/gc/shenandoah/TestJcmdHeapDump_aggressive/hs_err_pid650235.log
        [2024-12-07T00:35:29.842295115Z] Waiting for completion finished for process 651326

              wkemper William Kemper
              syan Sendao Yan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: