Issue metadata
Sign in to add a comment
|
Processes in some situations are reported as process ID 0 |
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Steps to reproduce the problem:
1. Listen to chrome.processes.onCreated
2. Go to chrome:extensions
Or
Open the Developer Tools (make sure it is started in docked mode)
What is the expected behavior?
{..., osProcessId: some real number}
What went wrong?
{..., osProcessId: 0}
WebStore page:
Did this work before? N/A
Chrome version: 60.0.3112.113 Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
,
Sep 12 2017
,
Sep 12 2017
,
Sep 12 2017
The Chrome task manager shows 0 as the process ID and no memory or CPU information when that happens, so it is not only an extension API issue. I think this is a regression.
,
Sep 12 2017
Thanks for the report! Assigning to afakhry@ for task manager triage.
,
Sep 12 2017
Nick, I thought you already fixed this issue in https://codereview.chromium.org/2961423002/. If this is Windows only, can you please take a look?
,
Sep 12 2017
#6 - since the issue affects more than just the task manager and that code seems pretty task manager specific, I am not sure that fix is related. Unless this task manager code feeds the chrome.processes API as well?
,
Sep 12 2017
The processes API is a client of the task manager.
,
Sep 12 2017
If you want to see the effects quickly, you can use this extension (inspect its background page) - https://github.com/phistuck/extraneous-process-detector-chrome-extension (It is benign without a Powershell script)
,
Sep 21 2017
,
Sep 26
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by phistuck@gmail.com
, Sep 12 2017