Confirmed users, Bureaucrats and Sysops emeriti
419
edits
Global nsICycleCollector service: Difference between revisions
Jump to navigation
Jump to search
Global nsICycleCollector service (view source)
Revision as of 00:46, 24 February 2006
, 24 February 2006→Problem overview
| Line 1: | Line 1: | ||
== Problem overview == | == Problem overview == | ||
When multiple XPCOM objects form a cycle but are otherwise disconnected from any live roots (pointers | When multiple XPCOM objects form a cycle but are otherwise disconnected from any live roots (pointers not embedded in XPCOM objects that a thread can find transitively from its static and local variables, e.g. local nsCOMPtr variables) it is considered a garbage cycle. Currently XPCOM cannot collect garbage cycles. This is a proposal to produce a collector for such cycles. | ||
Common sources of garbage cycles in XPCOM appear to be cycles between javascript objects and browser objects, particularly DOM objects. | Common sources of garbage cycles in XPCOM appear to be cycles between javascript objects and browser objects, particularly DOM objects. | ||
== Various requirements == | == Various requirements == | ||