Getting Heap Dump

This page describes getting a heap dump from the profiled application.


The heap dump can be taken whenever the profiler is connected to a process (see First Profiling Session for details on starting a profiling session), no matter what the current profiling mode is. However, to take a heap dump with minimal overhead on the profiled application, start a Telemetry profiling session - see Profiling Telemetry.

Once the profiling session runs, the heap dump can be taken by clicking the Heap dump button in Process section of the Profiler window toolbar or using the main IDE menu | Profile section.

Before the heap dump is taken, a location to save the file has to be provided. By default the heap dump is saved to the profiled project. Note that the dump file can be very large depending on the heap size, sometimes it's better to save it to a different location (temp folder is preselected).

Once the heap dump has been saved, the profiler offers to open it. Note that depending on the dump size it can take some time to open the file. Eventually the heap dump is opened in a separate window in the heap viewer.

Note: Taking heap dumps is not available for remote processes. You can use for example the VisualVM or Java VisualVM tool to take heap dump of a remote process, manually transfer it to the local system and open it in the IDE using the File | Open File... command in the main menu.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo