https://bugs.documentfoundation.org/show_bug.cgi?id=172804
--- Comment #4 from V Stuart Foote <[email protected]> --- (In reply to Xisco Faulí from comment #2) > OTOH, I was wondering, does Chrome hangs for you as well with the old > drivers ? No, Chrome had no issues. But then IIUC internally Chrome is very robust in its choice of rendering responding to "questionable" hw/driver combinations. I looked but didn't keep a listing of chrome://gpu with the 27.20.100.8853, I think it was using OpenGL. I snipped from Google AI query "how does chrome decide to use vulkan hw acceleration for rendering", seems relevant and maybe a clue of what LO could be doing: Google Chrome decides to use Vulkan for hardware acceleration by checking if your system meets its performance standards, driver stability tests, and feature requirements.Chrome follows a specific checklist to make this decision. Chrome verifies if you have enabled the master switch in settings. This is located at chrome://settings/system -> Use graphics acceleration when available. Chrome checks an internal database. If your specific GPU model or driver has a history of crashing, Chrome blocklists it and falls back to OpenGL or ANGLE (a translation layer). Driver Version: Chrome checks your driver version. Older drivers will often result in Vulkan being disabled automatically to prevent system crashes. Vulkan Support Test: Chrome runs a basic Vulkan initialization test. If your system cannot compile or load basic Vulkan commands, Chrome defaults to OpenGL. If your system passes, Chrome uses the Skia Renderer to draw web pages, and then uses Vulkan to quickly translate those graphics to your physical screen. -- You are receiving this mail because: You are the assignee for the bug.
