Ivan Rakov created IGNITE-11769: ----------------------------------- Summary: Investigate JVM crash in PDS Direct IO TeamCity suites Key: IGNITE-11769 URL: https://issues.apache.org/jira/browse/IGNITE-11769 Project: Ignite Issue Type: Bug Reporter: Ivan Rakov Fix For: 2.8
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 this crash. After some point, JVM stays dormant for 2 minutes and then process gets killed by OS signal {code:java} Process finished with exit code 134 (interrupted by signal 6: SIGABRT {code} and the following error messages can be dumped to stderr before process death {code:java} `corrupted double-linked list` `free(): corrupted unsorted chunks` {code} which appear to be libc error messages. Seems like Ignite corrupts virtual memory in sophisticated way which prevents normal JVM Crash flow. -- This message was sent by Atlassian JIRA (v7.6.3#76005)