Changes between Version 5 and Version 6 of Inspecting the GC heap


Ignore:
Timestamp:
Aug 23, 2018 9:55:51 PM (4 years ago)
Author:
Simon Fraser
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Inspecting the GC heap

    v5 v6  
    6666
    6767Finally there is the '''All Objects by Type''' section, that lists all the objects in the GC heap (thousands of them). Many of these are built-in objects and functions and not very interesting.
     68
     69Typically, if you're looking at a Document leak, you'll start with the '''Shortest paths to all HTMLDocuments''' section and just expand the HTMLDocument with the url that you care about. If you're combining this with debugging, you can use the pointer addresses too. In our case, we care about [http://localhost:8800/IndexedDB/value.htm] so expand that, and the reason for it staying alive is immediately clear; there's reference chain from: {{{IDBRequest cell 0x116c4b760 wrapped 0x12549e7e0 “url http://localhost:8800/IndexedDB/value.htm” (GC root—Weak sets, ActiveDOMObject with pending activity)}}} - note the ''ActiveDOMObject with pending activity''. So now we know to start debugging into IDBRequest objects and figuring out why they are left in a state of having pending activity.
     70
     71