Why is IntelliJ IDEA using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
IntelliJ IDEA runs on the Java virtual machine, whose maximum heap sets how much memory the IDE can use, and it analyzes your classes, dependencies and JDK to build an index for completion and navigation. That project analysis runs after you open or clone a project, switch branches, change plugins or generate many files, and it is the main source of CPU spikes. Help | Change Memory Settings adjusts the heap, and excluding generated folders reduces what has to be analyzed.
Why does IntelliJ IDEA use CPU after opening a project?
JetBrains calls this project analysis (earlier versions called it indexing). It maps your code, dependencies and JDK so completion, navigation and finding usages work. It runs after you open or clone a project, enable or disable plugins, switch branches, or make large external changes such as generating files during a build. Progress shows in the status bar.
Scanning files cannot be paused or canceled. Analyzing and indexing file contents can be paused and resumed. Builds started from the IDE run Gradle or Maven in separate java processes with their own memory.
How do you see and change IntelliJ IDEA's memory?
- Show the memory indicator. Right-click the status bar and select Memory Indicator. It shows how much of the heap the IDE is using.
- Change the heap. Choose Help | Change Memory Settings, set the new maximum, and click Save and Restart.
- Act on low-memory warnings. IntelliJ IDEA warns when free heap drops below 5% of the maximum after garbage collection. Click Adjust memory options in the warning to raise the limit.
- Exclude generated folders. In the Project tool window, right-click a folder of build output or generated code and choose Mark Directory As | Excluded. Excluded folders are not analyzed.
- Use shared indexes for big projects. Shared indexes let a team analyze a project once and reuse the index on other computers, so each Mac does less work after a checkout.
Should you edit idea.vmoptions in the app?
No. JetBrains notes that on macOS, editing IntelliJ IDEA.app/Contents/bin/idea.vmoptions violates the application signature, and the file is replaced on updates. Use Help | Change Memory Settings, or create your own copy in the configuration directory (or point the IDEA_VM_OPTIONS environment variable at one) to override JVM options.
When is IntelliJ IDEA's resource use a problem?
High CPU during project analysis and builds is expected. It is a problem when the memory indicator stays close to the maximum and the IDE pauses frequently (garbage collection cannot free enough), or when analysis restarts over and over without you changing anything. Raise the heap for the first; for the second, look for a build step or tool that keeps rewriting files inside the project.
How can Thrum help with IntelliJ IDEA?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much IntelliJ IDEA holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click IntelliJ IDEA in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
How do I give IntelliJ IDEA more memory on a Mac?
Choose Help | Change Memory Settings, enter a larger value and click Save and Restart. Do not edit the vmoptions file inside the app bundle.
Can I stop IntelliJ IDEA indexing?
Analyzing file contents can be paused and resumed from the status bar, but not canceled. The initial file scan cannot be paused.