Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 122217 Webpages with complex layer use hit memory limits
Starred by 4 users Project Member Reported by danakj@chromium.org, Apr 5 2012 Back to list
Status: Fixed
Owner:
Closed: Apr 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
See http://code.google.com/p/chromium/issues/detail?id=121605

This page http://acko.net/blog/this-is-your-brain-on-css/ is hitting our memory limits imposed on viewport size.

We now drop textures in background tabs, so we should increase this memory limit. While multiple windows will still fight for memory, we should have much less of a problem.

I propose we just limit on the hard bounds we have now, and drop the viewport-size-based restriction, for M19. (We will work on making real bounds for each tab in the future.)
 
Summary: Webpages with complex layer use hit memory limits (was: NULL)
Cc: epenner@chromium.org
I'm supportive of that approach.  I checked the brain-css page and it uses about 88MB of textures fullscreen in a 24" monitor whereas we only give it about 64MB.  Other sites that show issues, especially when the window size gets small are:

http://zaha-hadid.com/archive
http://www.kraftrecipes.com/recipes/sandwich/index.aspx

Neither of them are using unreasonable amounts of texture memory but at smaller window sizes we start dropping content.


Labels: WebKit-ID-83316
Project Member Comment 5 by bugdroid1@chromium.org, Apr 6 2012
Labels: -WebKit-ID-83316 WebKit-ID-83316-NEW
https://bugs.webkit.org/show_bug.cgi?id=83316
Status: Started
Project Member Comment 7 by bugdroid1@chromium.org, Apr 14 2012
Labels: -WebKit-ID-83316-NEW WebKit-ID-83316-RESOLVED WebKit-Rev-114191
https://bugs.webkit.org/show_bug.cgi?id=83316
http://trac.webkit.org/changeset/114191
Comment 8 by danakj@chromium.org, Apr 14 2012
Labels: ReleaseBlock-Stable Merge-Requested
Status: Fixed
Comment 9 by laforge@google.com, Apr 14 2012
Labels: -Merge-Requested
Let's see what this does in the Dev channel.  I'm admittedly a little scared of what the fall out will be from hitting the lower memory limits will be.

Removing merge-request, until we have data next week.
Sounds good thanks.
Labels: Merge-Requested
Ping for merge request.
Comment 12 by laforge@google.com, Apr 19 2012
Labels: -Merge-Requested Merge-Approved
Labels: -Merge-Approved Merge-Merged
Project Member Comment 14 by bugdroid1@chromium.org, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 15 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-WebKit -Mstone-19 -Feature-GPU-Compositing Cr-Content Cr-Internals-GPU-Compositing M-19
Project Member Comment 16 by bugdroid1@chromium.org, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 17 by bugdroid1@chromium.org, Apr 5 2013
Labels: -Cr-Internals-GPU-Compositing Cr-Internals-Compositing
Project Member Comment 18 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Sign in to add a comment