Massif Visualizer is an utility that - *who would guess that* - visualizes massif data. You run your application in Valgrind with `--tool=massif` and the open the generated `massif.out.%pid` in this application. You can also compress the log with Gzip or Bzip2 and open it transparently with the visualizer.
The application consists of three parts:
The Overview Chart
The first thing you will notice is a nice chart that displays the same as e.g. `ms_print` does in Ascii-Art: total memory consumption over time.
What Massif-Visualizer goes further is by additionally showing the top ten most cost-intensive locations in your code as a stacked graph below the total cost. The graph also reacts on user-interaction.
This view you can use for
- checking whether your application has memory leaks
- finding too expensive peaks
- finding locations that significantly contribute to the overall memory consumption of your application
The Snapshot Data Tree
Directly next to the above chart, you will see a tree with all of the massif data. The tree items are colored depending on their cost, with red opaque being the most interesting (peak) elements. Green/transparent items are negligible and do not add significant cost to your application.
You can also search the tree and when you select something in it, the snapshot gets highlighted in the overview chart and the call graph gets updated.
The Call Graph for Detailed Snapshots
Massif generates a few detailed snapshots that essentially make up the tree. If you want to get an overview in a more comfortable way than the simple tree view, switch over to the detailed snapshot tab and see
the tree visualized as a call graph. Zoom in, zoom out, use the birds eye view and see what contributes to a given snapshot. Note that function calls with the same memory cost are grouped to easily find the interesting parts.
Product's homepage
What's New in This Release: [ read full changelog ]
· translations into 18 languages
· hiding functions via context menu
· basic custom allocator support
· configurable precision of memory size display
· various optimizations and bug fixes
Find us on Google+
