A fatal error by co.elastic.apm.agent.process.ProcessHelper.startProcess

Our production Java applications on Spring Boot 3 + Java 21 Azul running on Tomcat 10.1.24. suddenly turned off completely after few days of running without problem caused by: co.elastic.apm.agent.process.ProcessHelper.startProcess. I'm using latest version of agent elastic-apm-agent-1.52.1.jar.

Elasticsearch version:
7.17.13

APM Server version:
7.17.13

APM Agent language and version:
elastic-apm-agent-1.52.1.jar

Original install method and version:
https://mvnrepository.com/artifact/co.elastic.apm/elastic-apm-agent/1.52.1

Is there anything special in your setup?
Here is my elasticapm.properties

application_packages=com.myapp
enable_log_correlation=true
circuit_breaker_enabled=true
environment=PROD
server_url=https://apm.mydomain
sanitize_field_names=password,passwd,pwd,secret,*key,*token*,*session*,*credit*,*card*,authorization,set-cookie,pw,pass,connect.sid,x-authorization,x-consumer,x-context
ignore_exceptions=mydomain.ExceptionName

We was running for few years without problem on Java 11 + apm java agent 1.28.4. After upgrade to Java 21 we noticed this error few days ago with apm agent version 1.51.0. Our few apps had error in Hazelcast thread in co.elastic.apm.agent.loginstr.reformatting.AbstractEcsReformattingHelper.onAppendEnter
So we decided upgrade to latest version 1.52.1 but next fatal error in application thread was in co.elastic.apm.agent.process.ProcessHelper.startProcess

Unexpected spontaneous shutdown of our applications is a very big complication.

Steps to reproduce:
We don't have steps to reproduce.

here are two examples of hs_err_pid files: gist:3d3f2199d1660c62e8d13d93cfdebe74 · GitHub

This is a known JVM 16+ bug, fixed in the latest JVM releases for both 17 and 21. Upgrade your 21 to the latest version

Thank you, we will try a we will let you know the results.