Bug 76045 - Web Inspector: [Chromium] Heap profiler need to track active DOM objects
Summary: Web Inspector: [Chromium] Heap profiler need to track active DOM objects
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 78411
  Show dependency tree / graph
 
Reported: 2012-01-11 02:48 PST by Mikhail Naganov
Modified: 2013-04-05 13:01 PDT (History)
11 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Naganov 2012-01-11 02:48:43 PST 
Active DOM objects are objects that have an internal state (e.g. XMLHttpRequest) and depending on the state may resist to be garbage-collected, even in case when they are not referenced. This way, Js leaks can occur, if such an object holds other objects.

See this report by Jochen Eisinger for details: https://docs.google.com/a/google.com/document/d/1Pd7hcFAUs_sFmpGumEkBonELlyU6diJAO9VXE0u6l7o/edit
Comment 1 jochen 2012-01-11 11:26:31 PST 
I filed issue 75859 for the actual issue I found: an ActiveDOMObject overrides hasPendingActivity() and essentially always returns true. That integration with the V8 garbage collector marks such objects as referenced, but the reference is not visible to the developer from devtools (in that specific case, you can still detect the presence of the object from js, e.g. if you start a version change transaction it would block even though there's seemingly no database around that could block the transaction)
Comment 2 Timothy Hatcher 2013-04-05 13:01:08 PDT 
Chromium and V8 have left the building. Won't fix.