'Lost UI shared context' Chrome error

Corion / WWW-Mechanize-Chrome

automate the Chrome browser

https://metacpan.org/release/WWW-Mechanize-Chrome

Artistic License 2.0

30 stars 12 forks source link

'Lost UI shared context' Chrome error #13

Closed sdondley closed 6 years ago

sdondley commented 6 years ago

When running tests, the following error is thrown throughout the tests:

[0706/042333.730708:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.

Occurs on both MacOS and Linux (Debian). The error doesn't cause any tests to fail and seems harmless. Not sure if there might be a way to get rid of it.

Corion commented 6 years ago

This is a problem that seems be more with Chrome / Chromium than the ways automating it. It also happens on WSL ( https://github.com/Microsoft/WSL/issues/3282 ) and with Puppeteer ( https://github.com/GoogleChrome/puppeteer/issues/1925 ).

Most likely it is something with Chrome Headless where the code expects a UI to be available, but which isn't available (due to being headless).

sdondley commented 6 years ago

I've been searching around for a command line switch that might suppress it. So far, no luck.

sdondley commented 6 years ago

I've addressed this issue by addressing it in the documentation: https://github.com/Corion/WWW-Mechanize-Chrome/pull/14/commits/1ff5e90bcb73146e1d9c986e56e44a05aa22203e