New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 717474 link

Starred by 4 users
Status: Fixed
Owner:
mvstan...@chromium.org
Closed: May 2017
Cc:
mlippautz@chromium.org
tnagel@chromium.org
█ hpayer@chromium.org
hablich@chromium.org
verwa...@chromium.org
u...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

High memory consumption in Docs and Gmail

Project Member Reported by hpayer@chromium.org, May 2 2017 
Several users reported high V8 heap memory on Google apps (>1G) observed e.g. on docs and Gmail on M58 (also on M57). I observed today a similar scenario with a very simple docs document on my machine.

Based on a heap snapshot (please reach out to me if you want access to the snapshot) it looks like that we are keeping way to many closures alive. The closures all have different shared function infos, different contexts, but the same native context. They all contain the same source string.

Interestingly, the Gmail and Docs snapshot show that similar functions are leaking. They always hang of an array (2) of the Window object. Maybe the closure compiler is triggering this pattern?

mvstanton, I am assigning this bug to you for now since this one may be related to your changes.

Comment 1 by mvstan...@chromium.org, May 2 2017

Status: Started (was: Assigned)

We are seeing that we accumulate an array on window[2] full of closures that point to the same script string (but always a new Script and SharedFunctionInfo). Each closure holds onto about 500K of data. These accumulate in bursts. It seems to be associated with clicking on a link in gmail that points to a Google Doc. Here is the call stack thus far...

 v8::internal::Factory::NewScript(v8::internal::Handle<v8::internal::String>) ()
 v8::internal::Compiler::GetFunctionFromEval(v8::internal::Handle<v8::internal::String>, 
 v8::internal::Compiler::GetFunctionFromString(v8::internal::Handle<v8::internal::Context>
 v8::internal::(anonymous namespace)::CreateDynamicFunction(v8::internal::Isolate*, const*) ()
 v8::internal::Builtin_FunctionConstructor()...

Comment 2 by hpayer@chromium.org, May 2 2017 

Issue 716428 has been merged into this issue.

Comment 3 by hpayer@chromium.org, May 2 2017

Summary: High memory consumption in Docs and Gmail (was: High memory consumption on Docs and Gmail)

Comment 4 by hpayer@chromium.org, May 2 2017 

Issue 715058 has been merged into this issue.

Comment 5 by verwa...@chromium.org, May 3 2017 

See http://b/37931051 for details on what I suspect is the issue.

Comment 6 by shrike@chromium.org, May 9 2017

Labels: Performance-Memory

Comment 7 by hpayer@chromium.org, May 10 2017

Status: Fixed (was: Started)
See http://b/37931051 for details. This was not a Chrome bug.
►

Sign in to add a comment