Issue metadata
Sign in to add a comment
|
GPU process rapidly increases memory usage when moving mouse around in devtools elements
Reported by
thex...@gmail.com,
Aug 7
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3510.2 Safari/537.36 Steps to reproduce the problem: 1. Open Devtools, open chrome's task manager 2. Move mouse around elements in devtools 3. Observe GPU process memory footprint rapidly increasing What is the expected behavior? What went wrong? I suspect Chrome started leaking memory about a month ago in dev channel, as I started seeing tab crashes, or tabs sometimes turning completely black when devtools was open. Earlier today, I was having issues with memory allocation in another program, and I looked at Windows 10's task manager, and there was 17Gb (out of 19gb) committed memory, after closing Chrome it dropped to 3gb. Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? Yes Chrome version: 70.0.3510.2 Channel: dev OS Version: 10.0 Flash Version:
,
Aug 8
Thanks for filing the issue. Unable to reproduce the issue on windows 10 using chrome latest dev-70.0.3514.0 as per C#0. Could you please check the issue by upgrading chrome to latest dev with clean profile & let us know your observations on the same.
,
Aug 8
I can indeed still reproduce it on 70.0.3514.0 using guest profile with all extensions disabled (as could be seen from the video). I'm on Windows 10 Insider 17730.rs5_release.
,
Aug 8
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 9
I'm testing 70.0.3516.0 and the situation is somewhat improved, but I'm still seeing the GPU process spike to near 700MB even on the Google homepage (or the About Chrome page). This is certainly better than the continuously growing memory usage in earlier development versions. That being said, I just tested Chrome stable and it looks like the memory usage is similar, but 700MB in the GPU process for a single, simple website seems quite a bit high to me.
,
Aug 24
Still observing this 70.0.3528.4. Some crash ids that are most likely related: 7dc8caf2764ad4fc 0d646eed3336ee1a aa5a5c20aa7e2fd8 9bd1b2af9be6dc4e 8b9f061d4b310cb4 0f4bf7c3b1528797 fb670247b224cdef
,
Aug 28
As per the above provided crash id (0d646eed3336ee1a), issue seems to be similar to #875790, hence merging into it. Please feel free to undup if it is not similar. Thanks..!
,
Aug 28
I can't verify because that issue is private.
,
Sep 5
@jmukthavaram@chromium.org So what is that issue you merged into? I can not view it. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by thex...@gmail.com
, Aug 7