Closed Bug 951796 Opened 11 years ago Closed 11 years ago

Investigate ghost windows with ICC

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mccr8, Assigned: mccr8)

References

Details

jst has been trying out ICC locally, and after running it for a day or so, he sees some ghost windows that go away if he does minimize memory usage, which certainly sounds like it could be an ICC issue. The first step will be for me to try to reproduce this locally. Then I'll want to look at CC logs to figure out what is holding the windows alive. If there's nothing, then it is probably an incremental root, which we don't log yet, so I need to fix that. Then I can compare it to the synch run that actually collects the window to find out what is the difference.
I'm getting one of these now, on a slashdot tab I closed a while back. I opened a slashdot article up in a new tab, which still around in a BF cache, in case that is relevant.
The slashdot leak didn't go away with a synch CC, though it still could be caused by ICC. I'm not sure why it was happening.
jst and I haven't seen this again.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.