JetBrains IDE VM Options

Analyze the running IDE first, then propose the smallest defensible .vmoptions delta. Do not create or edit the user's files. Treat a flag being accepted by a JVM as compatibility evidence, not as proof of a performance improvement.

Workflow

1. Establish the runtime and baseline

Read prerequisite-check.md. Identify the IDE product/build, actual boot runtime vendor/version/build/path, bundled-versus-custom status, OS, architecture, current effective command line and flags, current custom options, and the process showing the problem.

The IDE build number is context only. It does not prove which runtime is active. The project SDK/JDK is not the IDE boot runtime.

If the exact runtime is unavailable, give collection instructions and limit the answer to diagnostics or runtime-independent changes. Do not infer an unconfirmed JBR major from an IDE version.

2. Confirm the process boundary

Determine whether the symptom belongs to the local IDE process, a remote IDE backend, Gradle daemon, build process, test JVM, language server, terminal process, or another child process. IDE .vmoptions affect only the IDE process to which the file is applied.

Redirect out-of-scope process tuning to that process's own configuration. Never claim that an IDE heap or GC change fixes a Gradle or test JVM problem.