On Tue, Sep 11, 2012 at 10:45 PM, Ulan Degenbaev <[email protected]> wrote:
> This is strange. SunSpider on Chrome takes less that 64mb for me.
>
> Could type "chrome://version" in the address bar and paste the info here?
> What device and android are you running on?
>
We found the reason.
We modified chrome code for fast first paint.
The point is webkit's dispatchFirstLayout().
Original chromium don't paint according to this function.
But, we modifed this function to request paint to browser process.
So, whenever new IFrame is loading, paint is requested.
I think this makes renderer process consume a lot of memory.
Thank you.
Simon.
>
>
> On Tuesday, September 11, 2012 2:06:26 PM UTC+2, Simon Hong wrote:
>>
>> Hi,
>>
>> I'm running chromium on ARM-A9 with 512MB RAM.
>> When I running sunspider 0.9.1, renderer is dead by oom killer.
>>
>> That renderer eats all of system memory.
>> So, I changed the sunspider's javascript code.
>>
>> This function is what I modified.
>> When I remove first two lines, I cannot see any memory loss.
>> It works well.
>>
>> function reallyNext()
>> {
>> document.getElementById("**frameparent").innerHTML = "";
>> document.getElementById("**frameparent").innerHTML = "<iframe
>> id='testframe'>";
>> var testFrame = document.getElementById("**testframe");
>> testIndex++;
>> if (testIndex < tests.length) {
>> testFrame.contentDocument.**open();
>> testFrame.contentDocument.**write(testContents[testIndex])**;
>> testFrame.contentDocument.**close;
>> } else if (++currentRepeat < repeatCount) {
>> testIndex = 0;
>> testFrame.contentDocument.**open();
>> testFrame.contentDocument.**write(testContents[testIndex])**;
>> testFrame.contentDocument.**close;
>> } else {
>> finish();
>> }
>> }
>>
>>
>> What is the reason of this happening?
>> ARM environment?
>>
>> Please give me any advice.
>>
>> BR,
>> Simon.
>>
>> --
> v8-users mailing list
> [email protected]
> http://groups.google.com/group/v8-users
>
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
