Closed Bug 717557 Opened 13 years ago Closed 12 years ago

quite a few small cycles between XUL and JS

Categories

(Core :: XUL, defect)

Product:
Core
Component:
XUL
Version:
12 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 735342

People

(Reporter: smaug, Unassigned)

References

(Blocks 1 open bug)

Details

The cycle is something like:

0x7f17e13b12c0 [rc=10] nsGenericElement (XUL) tooltip
> 0x7f17d8ce5610 Preserved wrapper

0x7f17d8ce5610 [gc] JS Object (XULElement)
> 0x7f17d8ce55b0 
> 0x7f17d77f6eb0 xpc_GetJSPrivate(obj)

0x7f17d77f6eb0 [rc=1] XPCWrappedNative (XULElement)
> 0x7f17e13b12c0 mIdentity

0x7f17e13b12c0 [rc=10] nsGenericElement (XUL) tooltip
> 0x7f17d8ce5610 Preserved wrapper


We should be able to cut that cycle when the element is certainly black.
Is the element in a currently live document?  This sounds like something bug 717500 would solve.
Blocks: 716598
OS: Linux → All
Hardware: x86_64 → All
Though you may need more than that.  What happens when the preserved wrapper is black?  Is that a case where CanSkip will return true?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.