Received: by 10.42.41.9 with SMTP id n9mr6799862ice.29.1352786228461; Mon, 12 Nov 2012 21:57:08 -0800 (PST) X-BeenThere: google-chrome-developer-tools@googlegroups.com Received: by 10.42.84.2 with SMTP id j2ls10634804icl.0.gmail; Mon, 12 Nov 2012 21:57:07 -0800 (PST) Received: by 10.50.33.180 with SMTP id s20mr7778875igi.5.1352786227706; Mon, 12 Nov 2012 21:57:07 -0800 (PST) Received: by 10.50.33.180 with SMTP id s20mr7778874igi.5.1352786227691; Mon, 12 Nov 2012 21:57:07 -0800 (PST) Return-Path: Received: from mail-ia0-f173.google.com (mail-ia0-f173.google.com [209.85.210.173]) by gmr-mx.google.com with ESMTPS id d5si1393805iga.1.2012.11.12.21.57.06 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Nov 2012 21:57:06 -0800 (PST) Received-SPF: pass (google.com: domain of loi...@google.com designates 209.85.210.173 as permitted sender) client-ip=209.85.210.173; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of loi...@google.com designates 209.85.210.173 as permitted sender) smtp.mail=loi...@google.com; dkim=pass header...@google.com Received: by mail-ia0-f173.google.com with SMTP id m10so5961808iam.32 for ; Mon, 12 Nov 2012 21:57:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=j5tFeOgkW2a3oVcTT6GUcCH+80zIrm/Tzk07hW+luuY=; b=McGPekY79Urdmb29CLeRkC4PzXgUSWt6/8rcoMPbzr8E9zTUIS4f8kLpG3mXZ9GuYG UbKLjii/I4oe2RrA531c4IJBYIw1H0xIqQEWU7hYJQcLtZojWzZ6eL6B8Pad3PaopDlg kAivDRlqYU4ZQAa2SReqX71hRVhlbbaYQuHEj2M96kxifnE5CpRcgJBqHNW9u3XVLqiX TjHCj27TGvTQx5Nnn+zJ7A5hrxCbbtyfiVt40eKqZ0xAkHIi5z4o0P5RGLirlZLltiTL ZXGcFey7fQ/RAUXkLEC2buEzwtNZDcZmlicvy0J8iPZYXdXcJEyMkhGPOMmR2yN4chIG 6TEw== d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=j5tFeOgkW2a3oVcTT6GUcCH+80zIrm/Tzk07hW+luuY=; b=bHxBdNBM3M0+Ez8mBrD31Gr/pWOhcwbq6cVqxjPtsW+IEoKJSwCHWKzQL5lKzuDwZI yCv+k5iOXa2wh1vvomqOG73o6yq69aRSa47jRW2O1SgwsaAceFKo98sdr9WLjkcdITlB 3chrCi85yS/hvWOKGSdC7/P2jVxpa0ZIniVuRT3B8szfJ8Hjc2FLbldlBlGX9lkGDe1Z 5p5AeaOXyy/VbS3BP4/XhtcHRHS+SM6kvpYVfrfKSmzRVx6wkca0ol97Cqbxk4rYZnxp JM7oNjBdFSQTANuPO0p9jvrf99nBpMRtDAkzJI4jHnFxSviCgyoLYcOJ0iV9GiXKBHmj OZSg== Received: by 10.43.83.1 with SMTP id ae1mr1093873icc.24.1352786226466; Mon, 12 Nov 2012 21:57:06 -0800 (PST) MIME-Version: 1.0 Sender: loi...@google.com Received: by 10.231.72.78 with HTTP; Mon, 12 Nov 2012 21:56:46 -0800 (PST) In-Reply-To: <7874ad82-604c-4265-8d55-75bb8513ba99@googlegroups.com> References: <7874ad82-604c-4265-8d55-75bb8513ba99@googlegroups.com> From: Ilya Tikhonovsky Date: Tue, 13 Nov 2012 09:56:46 +0400 Message-ID: Subject: Re: [Chrome DevTools] DevTools - native memory snapshot, my other bar is over 90% To: Thomas Toftborg Cc: Google Chrome Developer Tools Content-Type: multipart/alternative; boundary=bcaec519696d7c4eb104ce5a167a X-Gm-Message-State: ALoCoQnWIDO1ihj1T7fNqkewLorEkVSFZXkGB467PHZp2hpB1FrgsVPAGT/z9gX5+3RjaM6qrYS2xMvRjl3xufrmFuuBwaVEc4e8lHLlRuo4/pGT0KpWik3wc3VgMQKM2MtDM2t8L07nCNOB+gWeNX0ifaVeLLv/4pl2h8FTVdqziAKjJteBRXocecOzzTCjSG2Ll6k5fz8i1+Sh7lAOPecgRCLQ4AKrgmCfvGNbkS07vysZRIAFHos= --bcaec519696d7c4eb104ce5a167a Content-Type: text/plain; charset=ISO-8859-1 Unfortunately there is no screenshot in the mail. First of all please be sure that the tab with your site doesn't share renderer with other tabs. As the second step please be sure that your site doesn't have javascript leak. In almost all the cases a 'leaked object' in native memory has a small leaked wrapper in Javascript heap. See http://stackoverflow.com/questions/11969062/tool-to-track-down-javascript-memory-leak for the instructions. Regards, Tim. On Tue, Nov 13, 2012 at 2:04 AM, Thomas Toftborg wrote: > I am using the native memory snapshot in DevTools, in order to figure out > why my application is eating up a lot of memory. > I am not loading anything external, but my other bar is increasing a lot, > and after an hours run, it is using 90% = 100Megs of memory, and just keeps > increasing. I am more or less just adding and deleting dom nodes attached > to a javascript class over time. Let me know if you need more details. > > Please see attached screen shot for more details. > > The time in the top left is in seconds,and my javascript heap is not > increasing. > > Thomas > --bcaec519696d7c4eb104ce5a167a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Unfort= unately there is no screenshot in the mail.
First of all please be sure= that the tab with your site doesn't share renderer with other tabs.

As the second step please be sure that your site doesn&= #39;t have javascript leak.
In almost all the cases a 'leaked= object' in native memory has a small leaked wrapper in Javascript heap= .
See=A0http://stackoverflow.com/questions/119690= 62/tool-to-track-down-javascript-memory-leak=A0for the instructions.


Regards,
Tim.


On Tue, Nov 13, 2012 at 2:04 AM, Thomas = Toftborg <thomas.toftb...@gmail.com> wrote:
I am using the=A0native memory snapsho= t in DevTools, in order to figure out why my application is eating up a lot= of memory.
I am not loading any= thing external, but my other bar is increasing a lot, and after an hours ru= n, it is using 90% =3D 100Megs of memory, and just keeps increasing. I am m= ore or less just adding and deleting dom nodes attached to a javascript cla= ss over time. Let me know if you need more details.

Please see attached scr= een shot for more details.

The time in the t= op left is in seconds,and my javascript heap is not increasing.

Thomas

--bcaec519696d7c4eb104ce5a167a--