Memory View Section | ![]() ![]() |
![]() |
The memory view section contains the
|
![]() |
Unless "Record allocations on startup" has been selected in the Startup section of
the profiling settings dialog, data
acquisition has to be started manually by clicking on
![]()
Allocation data acquisition can be stopped by clicking on
The allocation recording state is shown in the status bar with a Restarting data acquisition resets all data in the the recorded objects view, the allocation call tree and the allocation hot spots view. Only the all objects view (JVMTI only) is not influenced by allocation recording.
When you
Note that you can also use a trigger and the "Start recording" and "Stop recording" actions to control allocation recording in a fine-grained and exact way. This is also useful for offline profiling. The heap walker will be able to display allocation call stack information only for recorded objects, otherwise the entire heap is displayed in the heap walker. |
![]() |
The memory views are integrated with the heap walker. The
![]() |
![]() ![]() |