1080011 - Lots of ghost windows and long cc times

Status: RESOLVED INCOMPLETE

(Core :: DOM: Core & HTML, defect)

Comment 1

[Andrew McCreight [:mccr8]]

Do you have any details here? :)

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

(I haven't seen any huge CC times recently. Medium <20ms CC times with 195 tabs + Chatzilla open)

Comment 3

[Jeff Muizelaar [:jrmuizel]]

http://people.mozilla.org/~jmuizelaar/cc-logs/cc-edges.92817.1412791478.log.xz
http://people.mozilla.org/~jmuizelaar/cc-logs/gc-edges.92817.1412791478.log.xz

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Attachment: memory-report.json.gz

Comment 5

[Jeff Muizelaar [:jrmuizel]]

I still have the browser running now, so if there's something else that you want gathered I can try.

Comment 6

[Andrew McCreight [:mccr8]]

A non-verbose CC log would be nice.  (I don't need the GC log for that one.)

Comment 7

[Andrew McCreight [:mccr8]]

One global window 0x12faaec00 [nsGlobalWindow #3449 inner https://bugzilla.mozilla.org/show_bug.cgi?id=1079398]
is beind held alive by a nsXPCWrappedJS (nsITimerCallback).

Comment 8

[Jeff Muizelaar [:jrmuizel]]

Here's the concise log: http://people.mozilla.org/~jmuizelaar/cc-logs/cc-edges.92817.1412794514.log.xz

Comment 9

[Andrew McCreight [:mccr8]]

Yeah, I'm seeing this, too.  I have 664 ghost windows now.  And my browser is super janky. :)

Jeff, are you using e10s?  I've found a patch that causes a bunch of leaked windows in e10s mochitests, maybe it is related.

Comment 10

[Andrew McCreight [:mccr8]]

It looks like you are not using e10s mode, judging by the memory report.

Comment 11

[Andrew McCreight [:mccr8]]

On telemetry, it looks like the 95% percentile of ghost windows increased from 3 to 5 on 10/4.

Comment 12

[Andrew McCreight [:mccr8]]

I'm pretty sure the issue I'm seeing is bug 1080301, because at least one of leaking windows are being held alive by an object element.  But as I said, Jeff's leak is non-e10s, and is via a nsITimerCallback.

Comment 13

[Andrew McCreight [:mccr8]]

The only thing (aside from canvas elements), which seems to be CCed properly, that looks like it owns nsITimerCallbacks is nsTimerImpl.  Could something be firing off a bunch of timers?  I'm not sure how we can diagnose that.

Comment 14

[Andrew McCreight [:mccr8]]

Jeff, does this happen regularly to you?  Do you have any idea how to reproduce it?

Comment 15

[Jeff Muizelaar [:jrmuizel]]

I haven't noticed it happening again. I'll write something here if it does.