This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 201004120251 ] [ JDK VERSION : 1.6.* ] -) Started NetBeans -) Started "Take a Snapshot" -) After completing the Initialscanning, I stopped profiling -) After that the OutOfMemoryError occured Dump-File is available at: http://www.MegaShare.com/1990367
Created attachment 97074 [details] The Log-File at this Exception
Over night I tried the following: -) Deleted my Cache-Directory (NetBeans-Userdir) -) Started NetBeans -) Started "Take a Snapshot" Today morning, I got the OOE again. HeapDump: http://www.MegaShare.com/1993712
Tested again with -Xmx950m (can give more, it´s a 32bit system. Heapdump + Message.log is available at http://www.MegaShare.com/1994002
Thanks for the report, but could you please create new snapshot that would contain less samples? To achieve this please take a snapshot for 5-6 mins.
Created attachment 97372 [details] Snapshot (48 seconds) It´s not so easy as you think (->Bug #184186). I hope you can use this nps.
Created attachment 97376 [details] An second Snapshot
The heap dumps look like issue 183832. However, the steps to reproduce do not match (you don't seem to use the IDE for long time and did not use editor, right?). Anyway, probably would be best to wait for fix of 183832 be integrated - can you please check if you get the OOME then? Thanks.
(In reply to comment #7) > The heap dumps look like issue 183832. However, the steps to reproduce do not > match (you don't seem to use the IDE for long time and did not use editor, > right?). Yes. I make nothing (only starting and profiling). > Anyway, probably would be best to wait for fix of 183832 be integrated > - can you please check if you get the OOME then? Thanks. Should I set then the property "-J-Dorg.netbeans.modules.editor.completion.CompletionImplProfile.level=ALL"?
You may set the switch, though if there are still problems they may be caused by something else then the CC profiling. Thanks. BTW the fix of bug 183832 is already in daily builds since 201004150201.
Tested a build 201004160201. It works fine. Thanks!
Reopened. I forgot to stop the Snapshot. -) Started NetBeans -) Started "Take a Snapshot.." -) After completing the Initialscanning, I stopped profiling -) Then the IDE was locked (No Window-response) for about 30 minutes(!). -) After that the OutOfMemoryError occured Heapdump is available at http://www.MegaShare.com/2016294
Created attachment 97531 [details] Message-log + Thread-Dumps while NB was locked. -) Message.log -) Thread-Dumps while NB was locked (Thread-Dump, from jvisualvm)
Created attachment 97589 [details] Logfile Tested again at current build (201004190200). OOE occured again. Dumpfile: http://www.MegaShare.com/2026003 -Dorg.netbeans.modules.editor.completion.CompletionImplProfile.level=ALL was set.
Ok, so this is now the same thing as bug 184186 or bug 183993. The new way the self-profiling snapshots are created and saved is more CPU and memory demanding. Finishing the snapshots takes longer and may lead to OutOfMemoryError. We need to do some fixes/optimizations here. Tomas Hurka said he would also look at the possibility to recover the original self-profiling that was more efficient - if profiler is available in the IDE (the new way does not need profiler at all, so self-profiling can work in Ruby or PHP IDE or in any NB platform application). *** This bug has been marked as a duplicate of bug 184186 ***