New issue
Advanced search Search tips

Issue 798491 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

ERROR:process_metrics.cc(105)] NOT IMPLEMENTED

Reported by grandstr...@gmail.com, Jan 2 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9901.77.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.97 Safari/537.36
Platform: 9901.77.0 (Official Build) stable-channel auron_paine

Steps to reproduce the problem:
Prereq: Chrome v63 Windows 10 Any version of Chromedriver and Python(Any Version)

Using the selenium api, open a new chrome instance and attempt to interact with it through the script. After a short period of time attempting to interact with the browser, the message: ERROR:process_metrics.cc(105)] NOT IMPLEMENTED is printed to the console over and over rather than the actual command being executed until either Chromedriver crashes or "Chrome stopped working" Confirmed with the Chromedriver team that this is an issue with Chrome v63, not Chromedriver. 

What is the expected behavior?
Interacting with the browser through the script should result in the browser doing what it was told to do, not print ERROR:process_metrics.cc(105)] NOT IMPLEMENTED then promptly crash. 

What went wrong?
open a new chrome instance and attempt to interact with it through the script. After a short period of time attempting to interact with the browser, the message: ERROR:process_metrics.cc(105)] NOT IMPLEMENTED is printed to the console over and over rather than the actual command being executed until either Chromedriver crashes or "Chrome stopped working" Confirmed with the Chromedriver team that this is an issue with Chrome v63, not Chromedriver

Did this work before? Yes 62.0.3202.97

Does this work in other browsers? Yes

Chrome version: 63.0.3239.108  Channel: stable
OS Version: 9901.77.0
Flash Version: 

Further material on this issue cna be found here: https://bugs.chromium.org/p/chromedriver/issues/detail?id=2165#c8

and here: 
https://github.com/SeleniumHQ/selenium/issues/5189 

and here:
https://github.com/timgrossmann/InstaPy/issues/1103

and here:
https://github.com/timgrossmann/InstaPy/issues/1054
 

Comment 1 by vsu...@google.com, Jan 10 2018

Labels: -OS-Chrome OS-Windows
Labels: Triaged-ET TE-NeedsTriageHelp Needs-Triage-M63
The issue seems to be out of TE-scope as it is related to chrome driver. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Components: Platform>DevTools
I think the NOT_IMPLEMENTED is a red herring. Perhaps devtools folks know what the issue could be as the chromedriver people seemed to punt on this.

Comment 4 by l...@chromium.org, Jan 31 2018

Cc: lushnikov@chromium.org
Components: Tests>WebDriver
Cc: -lushnikov@chromium.org johnchen@chromium.org
Components: -Platform>DevTools
process_metrics.cc could be unrelated.

John, did you look into it? Do you know what is going on here?
The error message came https://cs.chromium.org/chromium/src/base/process/process_metrics.cc?type=cs&q=process_metrics.cc&sq=package:chromium&l=109, where the ProcessMetrics::GetIdleWakeupsPerSecond method is not implemented on Windows. However I'm not sure when this method gets calls, and haven't found a reliable way to repro it.
Hy I have updated my chrome to version: 64 and now it stoped sending me this (ERROR:process_metrics.cc(105)] NOT IMPLEMENTED) error. 
Can confirm, V64 seems to fix the issue.
Status: Fixed (was: Unconfirmed)
Closing based on previous comment.
 Issue 798673  has been merged into this issue.

Sign in to add a comment