JetBrains IDE crashes randomly with SentinelOne agent injected into the JVM

Symptoms

JetBrains IDE on Windows crashes unexpectedly, often after extended uptime. The crash report (java_error_in_idea_<pid>.log) shows a native failure like

# Native memory allocation (malloc) failed to allocate <N> bytes. Error detail: Chunk::new 

or an EXCEPTION_ACCESS_VIOLATION.

The crash report confirms the SentinelOne agent is attached to the IDE:

• The JVM command line contains an -agentpath entry such as -agentpath:C:\Program Files\SentinelOne\Sentinel Agent <version>\SentinelJava64.dll=extendedCapabilities.
• The loaded modules list includes SentinelJava64.dll, InProcessClient64.dll, and SentinelAmsi64.dll.

Cause

SentinelOne injects a JVMTI agent (SentinelJava64.dll) into every Java process on the machine, including the IDE, and hooks native operating-system calls. This third-party instrumentation can destabilize the JVM's native memory allocation and cause native crashes that are unrelated to the IDE's Java heap usage. No IDE startup option or .vmoptions change prevents the injection, because the agent is attached by the endpoint-protection software, not by the IDE.

Resolution

The exclusion must be configured on the SentinelOne side by the IT or security team. It cannot be resolved from within the IDE.

1. In the SentinelOne management console, add a per-process exclusion for the IDE executable, for example idea64.exe (or pycharm64.exe, goland64.exe, and so on).
2. Include the bundled JetBrains Runtime so that child Java processes are also covered. The runtime ships under the IDE installation folder (...\jbr\) and under %LOCALAPPDATA%\JetBrains\.
3. Apply the policy and restart the IDE.

After the exclusion is active, verify that new java_error_in_idea_*.log crash reports no longer contain a SentinelJava64.dll -agentpath entry, and confirm that the crashes have stopped.

Related articles:

• How to exclude IDE folders from the security scan
• Random JRE crashes when SentinelOne Agent is used (TeamCity server)