IntelliJ IDEA 2025.3.1.1 Emergency Fix: Resolving Maven Freeze and WSL2 Config Loss

The author notes that IntelliJ IDEA’s rapid update cadence merged the Ultimate and Community editions, then quickly released an emergency 2025.3.1 update fixing over 200 issues and rolling back a database query feature.

Core Issue 1: Maven project opening freezes or runs out of memory

Symptoms

Crash on startup : after updating to 2025.3.1, opening large multi‑module Maven projects consumes more than 80% CPU and triggers an out‑of‑memory (OOM) crash within minutes, requiring forced termination via the task manager.

Thread deadlock : stack traces show many threads stuck in org.jetbrains.idea.maven.project.MavenProject$Companion.read.

Root cause analysis

Technically, MavenProjectsManager introduces a memory leak during project‑tree initialization. When an exception occurs (e.g., a cache file fails to read), the code repeatedly calls the read method. Because MavenProject does not override equals or hashCode, each read generates a unique key, inflating the internal hash map myModuleToAggregatorMapping and eventually exhausting memory.

Solution

Official fix : JetBrains resolved the issue in version 2025.3.1.1 and later; update the IDE to this version or newer.

Temporary work‑around (if you cannot update) :

Windows:

C:\Users\<username>\AppData\Local\JetBrains\IntelliJIdea2025.3\Maven

macOS: ~/Library/Caches/JetBrains/IntelliJIdea2025.3/Maven Linux: ~/.cache/JetBrains/IntelliJIdea2025.3/Maven Delete the Maven cache directory found above.

Disable file‑icon display via Settings | Editor | General | Editor Tabs → uncheck “Show file icon”, which reduces the cascade of IconProvider calls.

Core Issue 2: WSL2 project settings lost after IDE restart

Developers using WSL2 on Windows may encounter issue IJPL-225409, where Node.js interpreter, Run/Debug configurations, or Save Actions reset to defaults after closing and reopening the IDE, even though .idea/workspace.xml retains the configuration.

Solution

Official fix : JetBrains fixed this problem in 2025.3.1.1 and later; update the IDE.

Registry tweak :

Press Ctrl+Shift+A (or ⌘+Shift+A) to open the search dialog.

Type Registry and open the Registry editor.

Locate the option wsl.use.remote.agent.for.nio.filesystem.

Uncheck (disable) this option.

Restart the IDE; the WSL2 project settings persist.