javascript - Using Chrome's heap snapshot analyzer, how do I interpret dead-ends in the retainers view -



javascript - Using Chrome's heap snapshot analyzer, how do I interpret dead-ends in the retainers view -

i have single-page app leaking substantially. trying track downwards memory leaks using chrome's built-in memory profiling tools. heap snapshot has been giving me lot of success in tracking downwards quite few problematic code blocks, have reached bit of dead-end.

i have taken heap snapshot , isolated variable has leaked. open retainers view can see why object has not been garbage collected. seeing in retainers view (see below) confusing me. keeps reaching dead-end though claims given node in graph still has distance of 11. i'm not sure why won't allow me dig object when says there still depth there. expecting able expand way global variable on window object.

javascript performance google-chrome memory-leaks google-chrome-devtools

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -