New issue
Advanced search Search tips

Issue 869871 link

Starred by 5 users
Status: Duplicate
Merged: issue 873313
Owner:
haraken@chromium.org
Closed: Aug 24
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Memory Commit Charge keeps increasing when using Chrome

Reported by akarn...@gmail.com, Aug 1 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.12 Safari/537.36

Steps to reproduce the problem:
1. Keep Chrome running for some hours
2. Watch Youtube videos

What is the expected behavior?
The memory utilization "Commit Charge" keeps reasonably close to the physical memory usage

What went wrong?
Altough Chrome uses about 4 GB of physical memory on my system, the "Commit Charge" keeps increasing over time and eventually Windows will start paging and increasing the paging file size. I know it's Chrome because closing the application frees the "Commit Charge".

Did this work before? N/A 

Chrome version: 69.0.3497.12  Channel: dev
OS Version: 10.0
Flash Version: 

This happens on my Windows 7 x64 machine as well and has been happening since about two weeks.
commit_charge.png
24.0 KB View Download

Comment 1 by akarn...@gmail.com, Aug 1 

Memory usage just after closing Chrome in the attached image
commit_charge_2.png
24.1 KB View Download

Comment 2 by krajshree@chromium.org, Aug 2

Labels: Needs-Triage-M69

Comment 3 Deleted

Comment 4 by evo...@gmail.com, Aug 3 

I see same issue after updated to 69 beta (69.0.3497.23) today.
Easiest way to catch it for me is to run chrome for some time with opened few twitch live streams.

Comment 5 by evo...@gmail.com, Aug 4 

Not sure if this will help, but here is the dump from "Save dump" button taken at chrome://memory-internals/ when windows started to show low memory warning.
trace_with_heap_dump.json.gz
100 KB Download

Comment 6 by evo...@gmail.com, Aug 5 

Another dump and a screenshot before and after closing the chrome.
trace_with_heap_dump.json.gz
101 KB Download
memory.png
64.8 KB View Download

Comment 7 by mkte...@gmail.com, Aug 24

Cc: haraken@chromium.org
 Issue 874099  has been merged into this issue.

Comment 8 by mkte...@gmail.com, Aug 24

Cc: -haraken@chromium.org
Components: Blink>MemoryAllocator
Labels: -Type-Bug -Needs-Triage-M69 FoundIn-69 M-69 Type-Bug-Regression
Owner: haraken@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 9 by mkte...@gmail.com, Aug 24 

 Issue 876707  may be related, though it's on Chrome OS.

Comment 10 by mkte...@gmail.com, Aug 24

Mergedinto: 873313
Status: Duplicate (was: Assigned)
...And on further searching, it looks like this has been fixed in  Issue 873313  for the latest beta release.  Sorry for the chain-merging!
►

Sign in to add a comment