Duplicate of  issue 739772  ?

I am also running WebRoot SecureAnywhere, as the users in 739772 are doing; however, my CPU does not seem to be involved (see screen shot).

Unable to reproduce this issue on reported version 61.0.3163.100 and latest canary 63.0.3239.6 using Windows 10 
@ shellicarol: Could you please retry the scenario by removing all extensions.

If the issue stills persist, it would be great if you could provide chrome://gpu details and a "memory-infra" trace. When the system gets in this state:

1) Navigate to about:tracing
2) hit "record" in the upper left
3) select ""manually select settings""
4) Make sure all checkmarks are clear other than "memory-infra" in the right column
5) hit record and allow the trace to run for ~30s before stopping it.
6) save the trace (upper left-hand corner) and attach here

cc'ing ericrk@ from  Issue 739772  for inputs and further debugging of this

Latest update.... 

Before I removed all the extensions, I disabled them sequentially, to see if I could get the problem to stop. When I disabled the "Docs", "Sheets" and "Slides" extensions, the problem seemed to subside for a while.

But just today, something even stranger is happening. I have attached two files. Resource Monitor shows that some Chrome process is taking nearly 2GB of RAM. However, Chrome's Task Manager is showing no such process. I've attached screen shots of both.

I've also attached the Chrome GPU Details and the memory-infra trace, as you requested. 

Thank you,
Shelli

Deleted: Resource-Monitor.gif 56.3 KB

	Resource-Monitor.gif 56.3 KB View Download

Deleted: Chrome-Task-Manager.gif 30.9 KB

	Chrome-Task-Manager.gif 30.9 KB View Download

Deleted: Chrome GPU Details.txt 10.8 KB

Chrome GPU Details.txt 10.8 KB View Download

Deleted: trace_Chrome_Memory_Dump.json.gz 1.7 MB

trace_Chrome_Memory_Dump.json.gz 1.7 MB Download

Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I rebooted and now the GPU process is going through the roof again, so apparently, disabling the Google Drive extensions didn't solve the problem. At least both the Resource Monitor and the Task Manager currently agree on what is happening. I ran GPU details and another memory trace and attached them, just in case any meaningful differences can be discerned from before and after the reboot.

In the meantime, I'll keep cycling through the extensions to see if I can get the behavior to stop.

Deleted: Chrome GPU Details 2.txt 10.8 KB

Chrome GPU Details 2.txt 10.8 KB View Download

Deleted: trace_Chrome_Memory_Dump_2.json.gz 1.1 MB

trace_Chrome_Memory_Dump_2.json.gz 1.1 MB Download

shellicarol@ Thanks for the feedback.

Retired the issue again on Windows 7, 10 and Mac OS 10.12.6 on the reported version 61.0.3163.100, latest Canary 65.0.3309.0 and Stable 63.0.3239.108 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and  opened the Task Manager from Wrench menu -> More tools.
2. Opened few tabs and can see no increase in memory upto 1.9GB in the task Manager and Resource Monitor as well.

Attached are the screen shots for reference.

As the issue is not reproducible at TE-end, removing the 'Needs-Bisect' label.

Requesting someone from Internals>GPU team to please look into this issue and help in further triaging.

Thanks..

++ Attachments

Deleted: 774855.png 73.3 KB

	774855.png 73.3 KB View Download

Deleted: 774855-RM.png 103 KB

	774855-RM.png 103 KB View Download

->vmiura to find a Windows owner for this.

An ETW trace of this may show where the memory is going. If using UIforETW (recommended, see go/etw) then please go to UIforETW's Settings dialog and check "VirtualAlloc stack always" before grabbing a trace. Also, I recommend "Tracing to file" instead of the default of "Circular buffer tracing", selected in the main window. A 20-30 s trace should be sufficient.

zmo@ could you please take a look?

Ligi, do we have a Win7 machine with Intel GPU that we can try to reproduce this issue?

shellicarol@gmail.com: both your trace files I can't unzip. It seems the data are corrupted. Can you upload the json files directly?

I'm out of town but I can do that next week when I'm back.

Hmmm, I didn't zip them. The Chrome trace is zipping them. How do I get
Chrome NOT to zip them?

By the way, I think I can provide a little more detail to the pattern.

1) My computer becomes sluggish.
2) I see that MalwareBytes is also creeping up in RAM usage (approaching
300MB).
3) I reboot.
4) The GPU process immediately goes nuts.
5) I reboot again.
6) All is fine for a while.

This pattern has repeated over several reboot cycles now.

Just for kicks, I tried shutting off MalwareBytes when my system became
sluggish.  The computer stopped being so sluggish, but simultaneously, that
weird situation recurred, in which ResMon reports Chrome windows are using
far more RAM than Chrome Task Manager shows.

Can you upload to Google drive and share the link here?

I have uploaded the memory dumps here:
https://drive.google.com/file/d/16yrclsLbDcHwxcKTmXHHqc--OJbgrHZZ/view?usp=sharing

and here: 
https://drive.google.com/file/d/11tjNx4xmZEyB0h_-IvOGsbM7wlsFcFNN/view?usp=sharing

Another update, since there was an early hint that WebRoot might be involved.....

WebRoot was causing other problems with my computer, freezing various stages of logging into a profile. So I reinstalled it completely. However, even after a complete reinstall of WebRoot, when I rebooted and started Chrome, the GPU process immediately went nuts again.

Apologies for the delay to get to this. Taking a look at the trace, we got 1.8G "Private Footprint" for GPU process. Per discussion with erikchen@, this was reported by Windows's Sysinternals VMMap, not Chrome's own counting.

There are two possibilities: 1) Chrome GPU is leaking 2) Graphics driver is leaking.

Although we can't rule out 1), since this happens almost immediately after launching Chrome, and I can't reproduce on my side (and this is the only bug report on this issue), it's more likely your driver is responsible.

If you are willing, I can walk you through a few steps to confirm if Chrome might be responsible, but honestly, upgrading to Win10 and update the driver might be a better option for you.

Mark as WontFix for now.

Speaking of WebRoot slowing Chrome down, I had an old version installed and found it was the cause of searches via Chrome's omnibox taking almost 10 seconds to display results.