Fixing IntelliJ IDEA 'Dumb Mode' Slowness: A Diagnostic Guide

Recognizing the condition

You open a file and Ctrl+Click does nothing. Find Usages returns no results, code completion offers only plain-text suggestions, and the status bar shows "Indexing..." or a banner reading that the IDE is in "Dumb Mode." Dumb Mode is IntelliJ IDEA's name for the degraded state it enters while background indexes are being built: because the indexes power navigation and smart completion, the IDE deliberately disables those features rather than give wrong answers. Short bursts after opening a project or switching branches are normal. The problem worth diagnosing is when indexing never finishes, restarts constantly, or the IDE becomes unresponsive during it.

The useful takeaway: Dumb Mode is a symptom, not a root cause. The fix depends on whether the trigger is a misconfigured project, corrupted caches, memory pressure, external file scanning, or a misbehaving plugin — and each has a distinct diagnostic signature.

Cause-to-symptom table

Likely cause	Typical signature
Generated or build-output folders indexed as sources	Indexing restarts after every build; huge file counts in the progress indicator
Corrupted index caches	Reindexing loops on the same files; errors in the log mentioning index or stub corruption
Insufficient IDE heap	Memory indicator pinned near the limit; frequent GC pauses; OutOfMemoryError in the log
Antivirus or desktop search scanning project/system dirs	Indexing is slow but CPU in the IDE is low; disk activity from an external scanner process
Third-party plugin triggering reindexing	Log shows repeated reindex entries tied to a plugin stack trace; problem started after a plugin install

Ordered checks

1. Confirm what is actually running. Watch the status bar progress indicator, then open Help > Diagnostic Tools (the exact name varies by release; some versions expose an activity monitor). Identify whether the busy process is indexing, a plugin background task, or garbage collection. This single observation rules out half the table above.
2. Check memory pressure. Enable the memory indicator in the status bar (right-click the status bar if it is hidden). If heap usage sits near the maximum during normal editing and the indicator jumps with frequent GC, memory is a contributing cause.
3. Read the log. Use Help > Show Log in Explorer/Finder to open the log directory and search idea.log for repeated "reindex" cycles, OutOfMemoryError, or recurring stack traces naming a plugin class. A reindex loop that always restarts on the same file set points at caches or project configuration; a stack trace naming a plugin points at the plugin.
4. Check external interference. While indexing runs, watch your OS task manager. If an antivirus or search-indexing process shows heavy disk I/O against your project or the IDE system directory, that is your bottleneck.

Fixes matched to findings

Indexing restarts after every build

Build output and generated sources are being indexed. Right-click the folder in the Project view and choose Mark Directory as > Excluded (or configure it in Project Structure > Modules). Typical candidates: target, build, out, node_modules, generated code directories. Build tools like Maven and Gradle usually mark these correctly on import — if they do not, check that the project was imported through the build tool's model rather than opened as a bare directory.

Log shows index corruption or reindex loops

Invalidate the caches: File > Invalidate Caches, then restart. Be aware this forces a full reindex of the project and local history is cleared, so on a large monorepo plan for the rebuild time. Do this only when the log or looping behavior actually suggests corruption — it is not a general performance tune-up.

Memory indicator pinned, GC pauses, OutOfMemoryError

Raise the heap via Help > Change Memory Settings, which edits the IDE's JVM options and requires a restart. Doubling -Xmx (for example from 2048 MB to 4096 MB) is a reasonable step for large projects. Note the limitation: more heap fixes memory pressure only. It does nothing for an indexing loop caused by a misconfigured project root — you will just have a larger, still-looping IDE.

Antivirus or search indexer scanning IDE files

Add the project directories and the IDE's system and config directories to the scanner's exclusion list. The exact paths vary by OS and IDE version, so check the JetBrains documentation for your release. In managed corporate environments this usually requires security-team approval; raise it as a ticket with the specific paths rather than disabling protection yourself.

Plugin implicated in the log

Disable the suspect plugin under Settings > Plugins and restart. If you are unsure which one, disable recently installed or updated plugins first and re-enable them one at a time. If the problem disappears with a plugin disabled, report it to that plugin's vendor with the log excerpt.

Verifying the fix

After each change, reproduce the original workflow: open a file, use Ctrl+Click navigation and completion, and run a build. The expected result is that indexing completes once and stays done — the status bar returns to idle, smart features work, and the memory indicator stays comfortably below its limit during normal editing. If indexing restarts on every build again, the exclusion did not take effect or another generated directory is still included.

When to escalate

Escalate when you have done all of the following and the IDE is still slow or stuck: invalidated caches, excluded generated folders, raised the heap (with GC pressure confirmed), excluded directories from antivirus, and isolated plugins. At that point capture evidence before contacting anyone: use Help > Diagnostic Tools to take a thread dump or CPU snapshot while the slowness is happening, then file an issue in JetBrains' YouTrack tracker or contact support with the snapshot and idea.log attached. A CPU snapshot taken during the freeze is far more actionable than a description of the symptom — verify the file attaches correctly to the issue before submitting.

Menu names and diagnostic tool locations shift between IntelliJ IDEA releases and platforms, so confirm paths against the version you have installed via Help > About.