C
C
crazyjs2015-04-15 22:26:48
JavaScript
crazyjs, 2015-04-15 22:26:48

Explain the situation with memory leak detection in dev tools?

The first thing I googled about it - I already read it (the article is from the Yandex blog, so it’s not worth suggesting)

I want to understand if my timeline is growing memory consumption, and then I click on stop and look - we haven’t dropped to baseline => maybe leak (or GC has not worked yet)

BUT: is it worth pressing the collector button and then stopping the process and already analyzing - if it falls to baseline, then there is no leak

Just snapshots show growth all the time (after every 10 actions, each subsequent snapshop shows more and more memory ) and if you turn on the timeline and click on the picker, then everything will return to normal. I can't figure out what to believe?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Sergey, 2015-04-15
@crazyjs

Well, let's talk. If you ordered to collect the garbage and he gathered and left, then the collector himself would have cleaned everything if the memory had become small. You just didn't wait for this moment. On the other hand, if after manual garbage collection the memory has not dropped to the baseline, then there is a possibility of a memory leak.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question