javascript - Isolating memory leaks with Chrome Dev Tools nowadays -
the other day trying use famous three-snapshot-technique described addy osmani in this post. not suspect have normal precaution tend them before launching new application. i've used multiple times without issues.
however, in latest versions of chrome, seems comparison view between heap allocations no longer possible can't see what's retained between them that's causing leak.
attaching 1 screenshot quoted article , 1 screenshot machine.
allocation comparison
no allocation comparison :(
chrome version latest stable mac "36.0.1985.143" @ time of writing. i've tried canary , doesn't work.
any ideas of what's approach nowadays changed chrome?
you need select take heap snapshot checkbox, not record heap allocations. can choose comparison choose between shapshots compare.
Comments
Post a Comment