What Is Being Indexed And Causing OutOfMemory Errors?
I have Xmx set to 1150m (still on 32bit XP :O) and I am regularly getting out of memory errors.
e.g. in the last 2 hours I have 12 idea.log files and 27 instances of java.lang.OutOfMemoryError
At the moment I am editing gradle files, running builds and syncronising the views.
After out of memory IDEA restart and takes ages to index.
How can I find out what is being indexed?
I found these lines in the IDEA log:
2014-11-17 18:16:53,725 [ 19266] INFO - ellij.vfs.persistent.FSRecords - Filesystem storage is corrupted or does not exist. [Re]Building. Reason: Corruption marker file found
2014-11-17 18:20:48,145 [ 253686] INFO - indexing.UnindexedFilesUpdater - Unindexed files update started: 420429 files to update
Does attaching sources cause extra indexing and potential out of memory?
请先登录再写评论。
All files in project except in excluded directories in the project are being indexed, same story with libraries' sources / binaries.
Please upload zipped OOME memory dump for us to investigate.
When you increase Java heap (-Xmx) you at the same time decrease Java non-heap memory and this can cause OOM as well. So may be decreasing -Xmx to 500m or 700m will help.
I'm not sure that is correct.
idea.exe.vmoptions specifies the following so as far as I understand it, the non-heap is not affected by Xmx in this case.
Removing lots of unused plugins seems to have helped and I havent had a crash in the last week or so.
Do you want me to upload the memory dump here? Where do I find it?
You need to have -XX:+HeapDumpOnOutOfMemoryError in vmoptions (memory snapshot section @ https://intellij-support.jetbrains.com/entries/29983118-Reporting-performance-problems) and hprof file is created usually in current directory of the launched process