Both PDS Direct IO suites periodically fail with JVM crash.
The issue can be reproduced on Linux machine by running IgnitePdsWithTtlTest#testTtlIsAppliedAfterRestart using ignite-direct-io classpath.
The investigation is complicated because JVM crash report is not generated during crash. After some point, JVM stays dormant for 2 minutes (waiting for JVM crash handling activities timeout) and then the process gets killed
and the following error messages can be dumped to stderr before process death
which appear to be libc error messages. Seems like Ignite corrupts virtual memory in sophisticated way which prevents normal JVM crash flow.