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.
Product Version = NetBeans IDE 6.0 Beta 1 (Build 200709111000) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06; Sun Microsystems Inc. NetBeans was configured with "-Xmx1024m" option. However, it failed to save third snapshot of profiled JavaFX module in memory allocation mode with stack traces enabled. There were strange "overflow!" lines in messages.log. Although it displayed "Not enough memory to save snapshot" warnings it was able to dump heap, open it in heapwalker and even perform rule-based analysis. No OutOfMemory errors were reported in logs.
Created attachment 49752 [details] messages.log
I am not sure what is actual problem here. FYI: overflow! is debug output from memory lint.
From user's point of view it's strange that profiler is able to open snapshot, but fails to save it. No other messages are shown and it seems that there is enough memory for profiler since it is perfectly works with (probably) larger heap dump file. What would you recommend to do in this situation?
It looks like you mix snapshot and heap dump. Saving snapshot requires additional memory therefor you can take shapshot (it is held in only memory), but you cannot save it. I do not see any problem here. Start IDE with lager Xmx.
I was just thinking that 1024m of heap should be enough to handle profiling snapshots. It seems that I was wrong. Verified
Reopening as ENHANCEMENT. It would be nice if profiler was able to save already opened snapshot.