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.
We need to be able to grab a snapshot of the JVM state right before shutdown. In my case I am getting a nasty OutOfMemoryException (or Error, I forget) which causes a shutdown and I need to be able to view a snapshot at this point of failure, including the stack-traces for all allocations. I don't think this is currently possible for me to do.
This would indeed be useful, specifically in case when hunting for reasons for getting OOM errors. It will be hard to implement though, as large portion of the agent is in fact a Java code running inside the same VM. I'll keep this open for further research on whether there are ways to implement this.
Well "in theory" if you reserve memory for OOME interception at initialization time, when it actually occurs you should be fine (since you don't need to allocate any more memory). This is likely not as easy as I just said but it's an idea :)
Note that automatic dumping the heap and opening in HeapWalker on OOME is already available in Profiler 6.0 devbuilds.
Guys, correct me if I'm wrong, but isn't this feature implemented in 6.1?
Milestone cleanup: future->next
A .hprof heap dump is generated if the profiled application crashes on OOME (customizable in Tools | Options | Miscellaneous | Profiler). The heap dump doesn't contain allocation stack traces but it contains paths to GC roots so a potential memory leak can be easily discovered. Already fixed from my viewpoint, please reopen if you really need the allocation stack traces.