[0329/092826.404:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
Reported by
josipkol...@gmail.com,
Mar 29 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Start the Google Chrome browser 2. Initialize new ChromeOptions object 3. Add arguments to ChromeOptions object 4. Create Chrome driver service and store it in a variable 5. Initialize new ChromeDriver object and pass Chrome driver service and ChromeOptions as parameters What is the expected behavior? Google Chrome opens without showing an error in console window when initializing a ChromeDriver. What went wrong? Google Chrome shows an error in console window when initializing a ChromeDriver: [0329/092826.404:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain Did this work before? Yes 56.0.2924 Chrome version: 57.0.2987.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Mar 30 2017
same for me ~:> chromium-browser-stable [28663:28663:0330/191656.661568:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain [28663:28663:0330/191656.661690:ERROR:gpu_child_thread.cc(330)] Exiting GPU process due to errors during initialization
,
Mar 31 2017
Could anybody from dev team please look into this issue. Thanks.
,
Apr 21 2017
I am also seeing this error (on Linux). In my case I'm using CEF (Chromium Embedded Framework). This error message doesn't seem to cause any real issue, everything works fine, I have two GPU processes running good. I see this error message every time just after running CEF message loop. CEF initialization works fine, there is no error at that time, it appears only after message loop is run. Error started appearing after upgrade from CEF branch 2924 to branch 2987. OS: Ubuntu 14.04 64-bit CEF: 3.2987.1601.gf035232
,
Apr 28 2017
After upgrading to CEF v58 (Chrome/58.0.3029.81) this error message stopped appearing.
,
Mar 21 2018
Closing as per comment #5 |
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Mar 29 2017