Jenkins Server JVM crash with openjdk 17

Jenkins setup:

Jenkins Version 2.452.2
Operating System Ubuntu 24.04
Java Version Details

openjdk 17.0.11 2024-04-16
OpenJDK Runtime Environment (build 17.0.11+9-Ubuntu-1)
OpenJDK 64-Bit Server VM (build 17.0.11+9-Ubuntu-1, mixed mode, sharing)

I am observing notifications on Jenkins controller Server once in a week that says This Jenkins appears to have crashed . The Jenkins controller and agent nodes are working normally; however crash message looks concerning to me.

I am in the middle of migrating Jenkins jobs from legacy jenkins server to this server. So, I am not sure if I should continue the migration.

Crash Report Log

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (macroAssembler_x86.cpp:864), pid=320726, tid=320784
#  fatal error: DEBUG MESSAGE: illegal bytecode sequence - method not verified
#
# JRE version: OpenJDK Runtime Environment (17.0.11+9) (build 17.0.11+9-Ubuntu-1)
# Java VM: OpenJDK 64-Bit Server VM (17.0.11+9-Ubuntu-1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0xb11565]  MacroAssembler::debug64(char*, long, long*)+0x45
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /var/lib/jenkins/core.320726)
#
# If you would like to submit a bug report, please visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-17
#

---------------  S U M M A R Y ------------

Command Line: -Xmx10192m -Djava.awt.headless=true -Duser.timezone=Asia/Hong_Kong -Djdk.lang.Process.launchMechanism=vfork -Djava.net.preferIPv4Stack=true /usr/share/java/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080

Host: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz, 12 cores, 31G, Ubuntu 24.04 LTS
Time: Thu Jun 20 09:29:51 2024 HKT elapsed time: 12589.342359 seconds (0d 3h 29m 49s)

---------------  T H R E A D  ---------------

I have read below posts from the community; however the issue is different
1,2.