Status: Untriaged Owner: i...@chromium.org Labels: Type-Bug Pri-2 OS-All Area-WebKit Memory
New issue 24202 by pkast...@chromium.org: Investigate DOM multiplier for static pages http://code.google.com/p/chromium/issues/detail?id=24202 Load the HTML5 spec ( http://www.whatwg.org/specs/web-apps/current-work/ ) and then take a look at the renderer memory footprint. I get 155 MB +/- 20 MB. The spec is extremely large, but it's nowhere near 155 MB of text. The question is, is the multiplier here for the overhead of actually constructing the document/render trees acceptable? Someone from the memory task force should look at this, and in general perhaps find a way to express the "memory multiplier" for a page (something web authors might want to know). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---