ERROR:gpu_process_transport_factory.cc(1007)-Lost UI shared context : while initializing Chrome browser through ChromeDriver in Headless mode

by

When Headless Chrome was first released as GA (General Availability) by Google Team the article Getting Started with Headless Chrome mentioned that :

--disable-gpu \                # Temporarily needed if running on Windows.

A note was added as :

Right now, you’ll also want to include the --disable-gpu flag if you’re running on Windows.

As per the discussion Headless: make --disable-gpu flag unnecessary it was clear that :

The --disable-gpu flag is no longer necessary on Linux or Mac OSX. It will also become unnecessary on Windows as soon as the bug SwiftShader fails an assert on Windows in headless mode is fixed.

What happened under the hood?

As per the discussion headless: Switch from osmesa to SwiftShader as Google/Chromium team decided to ship SwiftShader with Chrome the team thought to start using it to render GL content in Headless Mode. This required a couple of changes as follows :

  • Skip GPU data collection in Headless Mode since SwiftShader isn’t considered a software implementation by that code which lead to a failure when we tried to retrieve information from the Window System.
  • Only skip GL initialization in InitializeStaticEGLInternal if we intend to use osmesa. SwiftShader requires initialization like the other non-software implementations.
  • SwiftShader is currently not supported on Mac OSX, so the team decided to continue to use the physical GPU in Headless Mode on that platform (unlike on other platforms where everything is software rendered).
  • So, to disable WebGL support in Headless Mode they decided to use –disable-gpu and –disable-software-rasterizer

The idea to Support WebGL in headless is still under discussion but SwiftShader fails an assert on Windows in headless mode with an error as :

[0117/125830.649194:ERROR:gpu_process_transport_factory.cc(1043)] Lost UI shared context.
DevTools listening on ws://127.0.0.1:37429/devtools/browser/1f0b2bf7-dfdd-44ac-9da7-f2659d352f0d

Conclusion

This error doesn’t impact your @Test and you can ignore the error for the time being.

More Related Contents:

  1. How to configure ChromeDriver to initiate Chrome browser in Headless mode through Selenium?
  2. ChromeDriver Error: ‘chromedriver’ executable needs to be in PATH [duplicate]
  3. selenium.common.exceptions.WebDriverException: Message: ‘chromedriver’ executable needs to be in PATH error with Headless Chrome
  4. Selenium: WebDriverException:Chrome failed to start: crashed as google-chrome is no longer running so ChromeDriver is assuming that Chrome has crashed
  5. WebDriverException: Message: ‘chromedriver’ executable needs to be in PATH while setting UserAgent through Selenium Chromedriver python
  6. unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed with ChromeDriver Selenium
  7. ‘Webdrivers’ executable may have wrong permissions. Please see https://sites.google.com/a/chromium.org/chromedriver/home
  8. WebDriverException: unknown error: cannot find Chrome binary error with Selenium in Python for older versions of Google Chrome
  9. How to allow or deny notification geo-location microphone camera pop up
  10. How to work with a specific version of ChromeDriver while Chrome Browser gets updated automatically through Python selenium
  11. WebDriverException: Message: Service chromedriver unexpectedly exited. Status code was: 127
  12. Error Message: ‘chromedriver’ executable needs to be PATH
  13. Filling in login forms in Instagram using selenium and webdriver (chrome) python OSX
  14. Clicking on Get Data button for Monthly Settlement Statistics on nseindia.com doesn’t fetch results using Selenium and Python
  15. How to set window size in Selenium Chrome Python
  16. Access Denied page with headless Chrome on Linux while headed Chrome works on windows using Selenium through Python
  17. Download file through Google Chrome in headless mode
  18. ‘list’ object has no attribute ‘get_attribute’ while iterating through WebElements
  19. Access to table objects on Webpage Using Python Selenium
  20. Selenium on MAC, Message: ‘chromedriver’ executable may have wrong permissions
  21. TypeError: ‘module’ object is not callable error with driver=webdriver(“C:\\Python34\\Lib\\site-packages\\selenium\\webdriver\\chromedriver.exe”)
  22. Undetected Chromedriver not loading correctly
  23. How to solve ‘Getting Default Adapter failed’ error when launching Chrome and try to access a webpage using the ChromeDriver using Selenium
  24. Chrome browser initiated through ChromeDriver gets detected
  25. WebDriverException: Service U:/Scraping/chromedriver.exe unexpectedly exited. Status code was: 1 while working with Chrome and Python
  26. Selenium – Python – AttributeError: ‘WebDriver’ object has no attribute ‘find_element_by_name’
  27. Handling “Accept Cookies” popup with Selenium in Python
  28. Python Selenium driver.execute_script WebDriverException: Message: unknown error: call function result missing ‘value’
  29. Automation Google login with python and selenium shows “”This browser or app may be not secure””
  30. selenium.common.exceptions.WebDriverException: Message: Can not connect to the Service chromedriver.exe while opening chrome browser

Leave a Comment