GMail users: please dogfood debug builds
Robert O'Callahan
leaks when using GMail on trunk debug builds. The symptoms are that when
the GMail tab has been open (and used) for a few days, memory leaks and
the browser starts to feel sluggish. The sluggish feeling is caused by
frequent cycle-collector runs that block the main thread for a short
time every few seconds. I think it's related to GMail because the
"--DOMWindow" output in the console shows that hundreds of DOMWindows
(mostly with GMail URLs) are freed when I close the GMail tab.
This is a very bad bug, but apparently it has not been widely reported.
Maybe there's something peculiar in my setup that causes it, or maybe
people haven't been able to identify the problem accurately enough to
file a coherent bug report, or maybe it's a debug-only leak... Anyway,
if GMail users could dogfood debug builds for a while --- or are already
doing so --- I'd be very interested in hearing if they see this problem.
See bug 526897.
Thanks,
Rob
Alexander Limi
on GC issues and excessive CPU usage in Gmail in the past, so glad to see
that I'm not the only one seeing this. I'm an intense user of Gmail — three
instances running in parallel, always open — so I definitely see the memory
leaks (or what I think are memory leaks, at least.
I'll definitely give the experimental builds a spin.
Thanks for trying to figure this out! I've always had a suspicion that Gmail
is the cause (well, FF with Gmail) of what a lot of my friends are reporting
when it comes to spiraling mem usage and sluggishness. All of them run Gmail
all the time.
--
Alexander Limi · Firefox User Experience Team · http://limi.net
> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
Alexander Limi
else, currently consumes 443MB of RAM, and around 20% CPU (spiking to 45%
every few seconds) — just idling.
--
Alexander Limi · Firefox User Experience Team · http://limi.net
On Thu, Feb 18, 2010 at 9:29 PM, Alexander Limi <li...@mozilla.com> wrote:
> This is awesome, I'll definitely check it out. I've been filing several
> bugs on GC issues and excessive CPU usage in Gmail in the past, so glad to
> see that I'm not the only one seeing this. I'm an intense user of Gmail —
> three instances running in parallel, always open — so I definitely see the
> memory leaks (or what I think are memory leaks, at least.
>
> I'll definitely give the experimental builds a spin.
>
> Thanks for trying to figure this out! I've always had a suspicion that
> Gmail is the cause (well, FF with Gmail) of what a lot of my friends are
> reporting when it comes to spiraling mem usage and sluggishness. All of them
> run Gmail all the time.
>
> --
> Alexander Limi · Firefox User Experience Team · http://limi.net
>
>
>
>
> On Thu, Feb 18, 2010 at 7:48 PM, Robert O'Callahan <rob...@ocallahan.org>wrote:
>
Alexander Limi
shark-enabled builds, e.g. this one for Mac:
?
--
Alexander Limi · Firefox User Experience Team · http://limi.net
On Thu, Feb 18, 2010 at 9:37 PM, Alexander Limi <li...@mozilla.com> wrote:
> Also; very timely. My browser, running three Gmail instances and nothing
> else, currently consumes 443MB of RAM, and around 20% CPU (spiking to 45%
> every few seconds) — just idling.
>
>
> --
> Alexander Limi · Firefox User Experience Team · http://limi.net
>
>
>
> On Thu, Feb 18, 2010 at 9:29 PM, Alexander Limi <li...@mozilla.com> wrote:
>
>> This is awesome, I'll definitely check it out. I've been filing several
>> bugs on GC issues and excessive CPU usage in Gmail in the past, so glad to
>> see that I'm not the only one seeing this. I'm an intense user of Gmail —
>> three instances running in parallel, always open — so I definitely see the
>> memory leaks (or what I think are memory leaks, at least.
>>
>> I'll definitely give the experimental builds a spin.
>>
>> Thanks for trying to figure this out! I've always had a suspicion that
>> Gmail is the cause (well, FF with Gmail) of what a lot of my friends are
>> reporting when it comes to spiraling mem usage and sluggishness. All of them
>> run Gmail all the time.
>>
>> --
>> Alexander Limi · Firefox User Experience Team · http://limi.net
>>
>>
>>
>>
>> On Thu, Feb 18, 2010 at 7:48 PM, Robert O'Callahan <rob...@ocallahan.org>wrote:
>>
Robert O'Callahan
> Sorry to spam this thread, but by "debug builds", do you mean the
> shark-enabled builds, e.g. this one for Mac:
>
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.7a2pre.en-US.mac-shark.dmg
No, these tinderbox builds:
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-macosx-debug/1266538932/
Or you can make one yourself...
Rob
Alexander Limi
Ah, thanks.
Or you can make one yourself...
On my MacBook Air? I'll stick with the download. ;)
Thanks! Let me know if there's anything special I should look for, I haven't
run debug builds before, so I don't know if there's special stuff to enable
logging etc.
Robert O'Callahan
> Thanks! Let me know if there's anything special I should look for, I haven't
> run debug builds before, so I don't know if there's special stuff to enable
> logging etc.
Run the build from the terminal. You should have console output that
looks like this:
++DOMWINDOW == 106 (0x2bd2bed0) [serial = 945] [outer = 0x2769ec20]
++DOMWINDOW == 107 (0x281d42b0) [serial = 946] [outer = 0x2769ec20]
--DOMWINDOW == 106 (0x2bd2bed0) [serial = 945] [outer = 0x2769ec20] [url
= about:blank]
Use the build for a few days. Once you get into that state where it's
sluggish and you get frequent CPU spikes, note where you are in the
console output (I press enter several times to create some blank space),
then close your GMail tab(s) and wait for a few seconds for cycle
collection to kick in. If you're seeing what I'm seeing, the DOMWINDOW
count will decrease by some hundreds. Collect that output and attach it
as a comment in the bug.
Rob
Alexander Limi
<rob...@ocallahan.org>wrote:
> On 19/02/10 6:55 PM, Alexander Limi wrote:
Thanks. My build is already sluggish, 330MB of mem with only Gmail open &
constant 25% CPU usage with spikes to 80-90% every 3-5 seconds. But will run
it for a while and see if I can get the same kind of output.
Alexander Limi
> On Fri, Feb 19, 2010 at 12:26 AM, Robert O'Callahan <rob...@ocallahan.org
> > wrote:
>
>> Run the build from the terminal. You should have console output that looks
>> like this:
>> ++DOMWINDOW == 106 (0x2bd2bed0) [serial = 945] [outer = 0x2769ec20]
>> ++DOMWINDOW == 107 (0x281d42b0) [serial = 946] [outer = 0x2769ec20]
>> --DOMWINDOW == 106 (0x2bd2bed0) [serial = 945] [outer = 0x2769ec20] [url =
>> about:blank]
>>
>> Use the build for a few days. Once you get into that state where it's
>> sluggish and you get frequent CPU spikes, note where you are in the console
>> output (I press enter several times to create some blank space), then close
>> your GMail tab(s) and wait for a few seconds for cycle collection to kick
>> in. If you're seeing what I'm seeing, the DOMWINDOW count will decrease by
>> some hundreds. Collect that output and attach it as a comment in the bug.
>
>
> Thanks. My build is already sluggish, 330MB of mem with only Gmail open &
> constant 25% CPU usage with spikes to 80-90% every 3-5 seconds. But will run
> it for a while and see if I can get the same kind of output.
>
Posted my results after leaving it running for a couple of hours, this is
the kind of log you're looking for, right?
https://bug526897.bugzilla.mozilla.org/attachment.cgi?id=427744
Will try to use it over an entire day tomorrow if this seems like it
triggers the same issue. I didn't have any other tabs open when exiting, and
didn't use the browser for much else in that period.
Robert O'Callahan
> Posted my results after leaving it running for a couple of hours, this is
> the kind of log you're looking for, right?
> https://bug526897.bugzilla.mozilla.org/attachment.cgi?id=427744
Yes!
It's slightly more data if you just close the GMail tabs and record the
results before you quit.
It's also a bit more data if you leave the browser for longer before
closing the tab(s) and see if that has more DOMWindows released.
It's probably also a bit simpler if you just have one GMail tab.
Thanks!
Rob