## Memory View Section |

| The memory view section contains the all objects view (JVMTI only) The all objects view shows the dynamic class-resolved statistics for the current heap usage. This view is only visible if you profile with Java 1.5 (JVMTI). recorded objects view The recorded objects view shows the dynamic class-resolved statistics for the live and garbage collected objects that have been recorded. allocation call tree The allocation call tree shows the allocation tree for the current heap usage and garbage collected objects. allocation hot spots view The allocation hot spots view shows which methods are responsible for creating objects of a selected class.

| 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 Record allocation data in the tool bar or by selecting Profiler->Record allocation data from JProfiler's main menu. Bookmarks will be added when recording is started or stopped manually. Allocation data acquisition can be stopped by clicking on Stop recording allocation data in the tool bar or by selecting Profiler->Stop recording allocation data from JProfiler's main menu. The allocation recording state is shown in the status bar with a memory icon which is shown in gray when allocations are not recorded. Clicking on the memory icon will toggle allocation recording. 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 stop recording allocations, the recorded objects will still be tracked for garbage collection. For example, if all recorded objects are garbage collected, both the recorded objects view and the allocation call tree will be empty in their default view mode (live objects only). You can then still display all recorded objects if you switch to one of the other two view modes (garbage collected only or both live and garbage collected). 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 take heap snapshot with selection action on the toolbar, in the View and context menus takes a heap snapshot and creates an object set with the currently selected objects.