I am tasked with evaluating an outdated web application for potential memory leaks. Following some tutorial steps using Chrome DevTools, I came across strange behavior and wonder if anyone can explain.
My test page is a very simple document, just containing an iframe with an empty src attribute.
<!DOCTYPE html> <html> <head> <title>emty iframe test</title> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <style type="text/css"> #report01 { background-color:red; } </style> </head> <body> <iframe id='report01' class='report' src='' width="1000" height="200"></iframe> </body> </html>
When executing the memory timeline on this page, when updating via the context menu only inside the internal iframe ("Refresh Frame"), I see a constant increase in the number of DOM documents, as well as the DOM Node score.
I manually GC'ed at the end of the timeline, but not a single account will return to its original value. I have caching disabled while DevTools are open to avoid problems in this regard. I also tried applying the “3 snapshot” method to find out what was going on, but it gives me an empty list of results.
So, why are the timeline counters increasing, although logically there should be no leaks in this scenario?
source share