Ask HN: Chrome Devtool memory is not effective, do you feel the same way?t

When you check 'Heap Snapshot' in Devtool, Javascript VM instance show current memory. But if you're testing a memory intensive page, the page will make it latency.

* Stats.js capable to show memory occupation with no latency, I don't know why Devtool can't make it happen. * 'Allocation instrumentation on timeline' take timeline snapshot, but you can not watch memory usage when snapshotting.

Use Heap Snapshot take 2 memory snapshot to make a diff, and find out where memory leak. But when you testing a memory leaking suspicious page, it will show millions of objects like this:

Object@4863 Object@4865 Object@4867 Object@4869 Object@4871 Object@4873 Object@4875 Object@4877 Object@4879

* You can not identify which Class of these objects easily, even you examine the object hierarchy.

So, how do you use Devtool for memory leak hunting?