New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 804173 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Excessive amount of Chrome processes both while using and after closing (be it through task manager or the red x)

Reported by shiny....@gmail.com, Jan 21 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome/new tabs/new window
2. 
3. 

What is the expected behavior?
Background processes shouldn't stay open like this even after killing chrome.

What went wrong?
In the attached image, I can scroll down for 4 pages or so. I just open Chrome, and I think every time I open a new tab or window something processes slowly begin to accumulate. I have attached the command line in other comments below: every chrome are all of this format, with some codes at the end that vary slightly. These are all in background processes, and is unrelated to my extensions, none of which affect the outcome after having tested that disabling them does not change anything (PixivKit, Tampermonkey, uBlock Origin, and Viramate).

I have disabled background processes, so this is unrelated to that function.

I don't know how this started, but one day I opened up task manager when my computer started getting a bit slower and then I noticed this strange occurrence. Also, I believe that it has began to cause Chrome crashes if enough processes open up after a while, which may be related to even just opening up new tabs.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 10.0
Flash Version: 

The command line is

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=crashpad-handler "--user-data-dir=C:\Users\***\AppData\Local\Google\Chrome\User Data" /prefetch:7 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\***\AppData\Local\Google\Chrome\User Data\Crashpad" "--metrics-dir=C:\Users\***\AppData\Local\Google\Chrome\User Data" --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=63.0.3239.132 --initial-client-data=0x1d4,0x1d8,0x1dc,0x1d0,0x1e0,0x7ffa33825720,0x7ffa33825760,0x7ffa33825738

All the processes most likely share this format. I checked a random assortment of the several background processes and they were all like that with some minor changes at the end.
 
Taskmgr_2018-01-21_15-09-10.png
73.4 KB View Download
Cc: susanjun...@techmahindra.com
Labels: Needs-Triage-M63 Triaged-ET Needs-Feedback
shiny.ice@ Thanks for the issue.

Tested this issue on Windows 10 on the latest Canary 66.0.3328.0 and Stable 63.0.3239.132 and unable to reproduce this issue by following the below steps.

1. Launched Chrome and opened few tabs.
3. launched task manager and could observe no excess Chrome processes.
Attached is the screen shot for reference.

Request you to please retry this issue on a new Chrome profile without any flags/extensions and update the thread with the observations.
In case of any crashes on Chrome, request you to please provide the Crash ID from Chrome://crashes, which will help in further triaging of the issue.

Thanks..

804173.png
118 KB View Download

Comment 2 by shiny....@gmail.com, Jan 22 2018

It worked perfectly. Thanks!
Project Member

Comment 3 by sheriffbot@chromium.org, Jan 22 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjunia.boorgula@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
As per comment#2 from the reporter, as the issue is not seen now, hence closing it.

@Reporter:
Feel free to raise the new issue with proper repro steps if the issue is seen again.

Thanks!
Cc: viswatej...@techmahindra.com
Status: WontFix (was: Unconfirmed)

Sign in to add a comment