Serious Memory Leak
Ben
single tab is opened to Facebook it can reach 1GB of Private memory in
under 10 seconds.
I started experiencing the leak after enabling some GPU rendering
features in about:flags. Unfortunately, disabling the features didn't
help at all. I enabled and disabled them in this order: 1.) enable
Override software rendering list, enable Composited render layer
borders; 2.) disable Composited...borders, enable "Disable GPU vsync";
3.) disable all.
At some point, 3D canvas and PPAPI flash in renderer were enabled; they
were disabled in the last step, too. However, even with all the features
disabled, memory usage skyrocketed.
I've attached a video (leak.ogg) demonstrating the leak...it's not
time-compressed or time-lapse, it's (more or less) real-time.
About Version:
__Chromium 13.0.782.215 (package Release version 1.fc15)
__User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML,
like Gecko) Chrome/13.0.782.215 Safari/535.1
__Command Line /usr/lib64/chromium-browser/chromium-browser
--enable-plugins --enable-extensions --enable-user-scripts
--enable-printing --enable-sync --auto-ssl-client-auth
--flag-switches-begin --block-reading-third-party-cookies
--new-tab-page-4 --flag-switches-end
Nico Weber
can you open a bug on http://new.crbug.com (attach the video) and post
the bug number here?
Thanks,
Nico
> --
> Chromium Discussion mailing list: chromium...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-discuss
>
Ben
a fresh profile, and couldn't reproduce until after installing it.
Should I still file a bug?
Nico Weber
> Looks like a bug in (or triggered by) the LastPass extension. I tried in
> a fresh profile, and couldn't reproduce until after installing it.
Thanks for tracking this down. It's probably more useful to file this
with the LastPass authors then :-)
Nico