Hey. We recently discovered a problem with test runs on CI. It looks like this:

Execution failed for task ':my_feature:testDebugUnitTest'. org.gradle.process.internal.ExecException: Process 'Gradle Test Executor 41' finished with non-zero exit value 134
  This problem might be caused by incorrect test process configuration.
  Please refer to the test execution section in the User Manual at <https://docs.gradle.org/7.5.1/userguide/java_testing.html#sec:test_execution>
  
[18:36:11] :	 [Step 20/24] # A fatal error has been detected by the Java Runtime Environment:
[18:36:11] :	 [Step 20/24] #  SIGSEGV (0xb) at pc=0x00007f8dbcdb8056, pid=23042, tid=23050
[18:36:11] :	 [Step 20/24] # JRE version: OpenJDK Runtime Environment (11.0.15+10) (build 11.0.15+10-Ubuntu-0ubuntu0.20.04.1)
[18:36:11] :	 [Step 20/24] # Java VM: OpenJDK 64-Bit Server VM (11.0.15+10-Ubuntu-0ubuntu0.20.04.1, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
[18:36:11] :	 [Step 20/24] # Problematic frame:
[18:36:11] :	 [Step 20/24] # V  [libjvm.so+0xb6c056]  MetaspaceShared::find_archived_heap_object(oopDesc*)+0x36
[18:36:11] :	 [Step 20/24] # 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 /opt/teamcity/work/ec484a2826eb1643/app/my_feature/core.23042)
[18:36:11] :	 [Step 20/24] # An error report file with more information is saved as:
[18:36:11] :	 [Step 20/24] # /opt/teamcity/work/ec484a2826eb1643/app/my_feature/hs_err_pid23042.log
[18:36:11] :	 [Step 20/24] # If you would like to submit a bug report, please visit:
[18:36:11] :	 [Step 20/24] #   Unknown

I see it's somehow related to Metaspace and 134 error code is SIGABRT. I can play with configuration and add more metaspace, but I want to do it with at least some idea, It looks like a fatal error to me and not an OOM which can be tuned somehow. Did you saw something similar? Internet is not so helpful. p.s. Core dump is not easily accessible in my case, but even if it was i don't know what to look there for p.p.s. Problem is not reproducible locally with same tasks run, it just happens on CI from time to time