Product Version: NetBeans IDE Dev (Build 201206200001)
Java: 1.7.0_04; Java HotSpot(TM) Client VM 23.0-b21
System: Windows XP version 5.1 running on x86; Cp1252; en_NZ (nb)
Java debugging and idle.
Heap dump split files were created with 7-zip http://www.7-zip.org/ from a
single zip file. Sorry for this. I tried without success to upload to
Created attachment 121323 [details]
logs and heap dump part 1
Created attachment 121324 [details]
logs and heap dump part 2
Created attachment 121325 [details]
logs and heap dump part 3
Created attachment 121326 [details]
logs and heap dump part 4
Created attachment 121327 [details]
logs and heap dump part 5
reassign to performance team for evaluation
Please attach messages.log.
(In reply to comment #7)
> Please attach messages.log.
Ok, It is in the zip file.
I am sorry, but there is no sign of out-of-memory-error exception in heap dump and in messages.log(s) in the attached zip.
Can one not from the heap dump analyze where the memory is wasted without getting an OutOfMemoryError? The IDE became unresponsive and complained that it could no longer get enough memory to compile source files. That was fairly obvious to me.
I watched the memory display and decided to quit after garbage collection could no longer reduce memory below somewhere around 385MBytes. I think it is not normal that I have to re-start the IDE after a half a day to reclaim memory. That is because on my computer if I wait for OutOfMemoryError then this is very painful because with a single CPU, it may takes hours to record this and gracefully recover from it. I had to do that with issue 213860 which was fixed. Apparently my computer is good for detecting these things.
Do you have any suggestions, advice?
From the heap dump it is not quite clear what is going on. The only think we know is that your have very large maven project. Waiting for OOME will give us better info what is going on. It will also trigger generation of the heap dump.
Besides that you can try several things:
1) do not use full NetBeans distro. Use Java SE (or Java EE).
2) you are running on 32bit system where default Xmx is 384m. You can try to increase it to 700m.
Created attachment 121592 [details]
log minus heap dump in zip file
Ran out of memory with display 129.5 / 247.5MB which is much less after last time.
I added in <Install Dir>\etc\netbeans.conf
There is sufficient memory in my system (3GB physical, only 1 GB used, 2GB available)
This happened after opening a few files and cut and paste code. Please let me know if you need the heap dump. Can attach on Monday.
Created attachment 121593 [details]
Created attachment 121595 [details]
log files minus heap dump in zip file
Another out of memory error. Was openeing an HTML file while a Windows Explorer search was running. I/O would have been slow.
I now stopped using the build netbeans-trunk-nightly-201206280002-ml-windows.exe with the error and switched back to 7.1.2. In addition to the large Maven project, and a Java EE project, I opened a Java ME project. No problems.
Due to incorrect changes to netbeans.conf, you are still running with Xmx 384M and default MaxPermSize, which is 64M. Netbeans needs a least 256M MaxPermSize.
1) There is no need to change MaxPermSize
2) You forgot to add -J to -Xmx
3) Both "-J-XX:MaxPermSize=512m -Xmx800m" must be inside of double quotes of netbeans_default_options
For your testing, it is much easier to rollback all your changes to netbeans.conf file and run netbeans.exe from command line: