Google Chrome loses hardware acceleration after update to nvidia 535 drivers

Bug #2026295 reported by Daniel Eckl
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-535 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Google Chrome (114.0.5735.198) has no hardware acceleration anymore with nvidia-driver-535_535.54.03-0ubuntu0.23.04.2

Chrome log on chrome://gpu shows:
[8344:8344:0702/133010.886230:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process.
GpuProcessHost: The GPU process crashed!

Console output of chrome shows:
[8519:1:0702/133015.490076:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[8301:8301:0702/133015.506857:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133
[8372:1:0702/133018.997300:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[8411:1:0702/133033.519614:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[8301:8301:0702/133033.537284:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133
[8519:1:0702/133034.105681:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.
[8519:1:0702/133034.105831:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error

Tried setting __GL_THREADED_OPTIMIZATIONS=0 as a workaround which reportedly helps with a similar issue with steam CEF, but no change for this issue.

Rolling back to 530.41.03 and immediately hwaccel is back.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.