Memory/performance issues on Chrome on Windows |
||||||||||||||||
Issue descriptionChrome Version: 57.0.2987.133 (Official Build) (64-bit) OS: Windows URL (if applicable) where the memory bloat occurred: n/a Can you reproduce this memory bloat? Yes, whenever I use Chrome this week, the issue persists. What steps will reproduce this memory bloat (or if it's not reproducible, what were you doing until then)? (1) Open up a bunch of tabs (Gmail, Docs, Sheets, Slides, Calendar) (2) Have 5 separate Chrome windows open with 1-10 tabs each (3) Open Spotify and have it playing in the background. What is the expected result? Chrome should be fine and not slow. It's slow to the point where I often consider switching back to a Mac in order to be efficient and productive. What happens instead? Chrome is super slow, unresponsive at times, and has poor performance issues. I don't know if it's a memory problem. I have followed the steps as outlined in go/chrome-memory-debugging-steps. Attached the file as instructed.
,
Apr 21 2017
,
Apr 21 2017
I'm not seeing much CPU activity, except perhaps to gather the memory dump. Any idea what's going on here Erik?
,
Apr 21 2017
The memory dump looks relatively innocuous. ~5.3GB total resident on a machine that has 8GB total. Swap is showing up as 0, so I suspect we've failed to hook that metric up correctly. + rob: Given that we're in the same office, and there had been some theories on the last thread "Interesting memory warning on my Win10 laptop" about potential causes, could you follow up in person with Teresa?
,
Apr 21 2017
Rob, I scheduled some time on Monday for you to look at my machine in person (I'm WFH today).
,
Apr 24 2017
,
Apr 24 2017
,
Apr 24 2017
Sync'ed up with teresam@ and I'm working on getting her machine set up with some tools so we can attempt to investigate this on Windows. The admin rights request should be pending at this point.
,
Apr 26 2017
The snapshot above omits that Gmail was using about 1.5G and when relaunched, consumed around 300M. Summary: The system was loaded near the physical memory limit. (6-7G usage on an 8G machine) The symptoms here so far seemed classic of Windows thrashing (lots of processes, lots of pagefile reads and writes). There was also some fun ruby stuff running in the background with might have been IT running a script (the AntiVirus engine was busy scanning that too, also taking away from available IO). We might want to be more aggressive about purging background tabs and/or throttling them to help reduce the pagefile IO on the system.
,
May 11 2017
Capturing new trace of my system. Still very slow. Let me know if there are any useful insights. Hopefully I did this right.
,
Jun 20 2017
Chris, can you block this on the tab killing bug? It sounds like there's not much we're going to be able to do other than make this experience better.
,
Jul 5 2017
,
Sep 5 2017
,
Sep 20 2017
|
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by erikc...@chromium.org
, Apr 21 2017