Bug 102786 - Chromium Native Memory Profiler shows 5MB in Page.Image for about:blank
Summary: Chromium Native Memory Profiler shows 5MB in Page.Image for about:blank
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-20 02:32 PST by Eric Seidel (no email)
Modified: 2013-04-11 11:49 PDT (History)
7 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2012-11-20 02:32:28 PST 
Chromium Native Memory Profiler shows 5MB in Page.Image for about:blank

Page.Image 5 425 KiB  27.9%

That's of a 19MB total.

I'm not sure if that number is accurate or not, but it seems we have a problem either way. :)
Comment 1 Eric Seidel (no email) 2012-11-20 02:51:44 PST 
Here are all the lines which should be contributing to this number:
http://code.google.com/p/chromium/source/search?q=PlatformMemoryTypes%3A%3AImage&origq=PlatformMemoryTypes%3A%3AImage&btnG=Search+Trunk
Comment 2 jochen 2012-11-20 03:06:01 PST 
How large is the browser window you have? I would expect that during rendering, it keeps around an image of width x height x 2 bytes
Comment 3 Eric Seidel (no email) 2012-11-20 10:00:12 PST 
Changing the size of the window and snapshotting again does not seem to change this number.  I've tried with large and small windows, and they get 5MB pretty consistently.

My display is 2560 x 1600 and the window was at least 2/3 the size of the screen.  Suggesting that if the backing-store was counted, we should be seeing more like 10MB of storage, no?
Comment 4 Eric Seidel (no email) 2012-11-20 10:01:07 PST 
I suspect it may also be 5MB of images loaded to run the inspector?
Comment 5 Ilya Tikhonovsky 2012-11-20 23:40:19 PST 
(In reply to comment #4)
> I suspect it may also be 5MB of images loaded to run the inspector?

It could be canvas image used by InspectorOverlay
https://bugs.webkit.org/show_bug.cgi?id=99429 

Unfortunately we can't count this image as a part of Inspector block because we are not able to track the ownership of an object at the moment but we are working in this direction.
Comment 6 Ilya Tikhonovsky 2012-11-20 23:52:32 PST 
(In reply to comment #5)
> (In reply to comment #4)
> > I suspect it may also be 5MB of images loaded to run the inspector?
> 
> It could be canvas image used by InspectorOverlay
> https://bugs.webkit.org/show_bug.cgi?id=99429 
> 
> Unfortunately we can't count this image as a part of Inspector block because we are not able to track the ownership of an object at the moment but we are working in this direction.

The simplest way to reduce inspector data is
Comment 7 Ilya Tikhonovsky 2012-11-20 23:53:47 PST 
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > I suspect it may also be 5MB of images loaded to run the inspector?
> > 
> > It could be canvas image used by InspectorOverlay
> > https://bugs.webkit.org/show_bug.cgi?id=99429 
> > 
> > Unfortunately we can't count this image as a part of Inspector block because we are not able to track the ownership of an object at the moment but we are working in this direction.
> 
> The simplest way to reduce inspector data is

incidental comment