Issues (hard crashes) with Google's Chrome...
.. or is it Mesa and/or 'amdgpu'?
Hi guys.
Lately, I'd say for ~1 month, my Chrome has been really
misbehaving even to the point when becomes unresponsive and
I have to kill it.
Chrome shows log full of things , with:
-> $ google-chrome --enable-logging --v=1
of which most worrying are:
...
[149778:149778:0100/000000.007110:ERROR:external_vk_image_skia_representation.cc(151)]
BeginAccess failed
[149778:149778:0100/000000.045833:FATAL:external_vk_image_gl_representation.cc(79)]
Unable to create an ExternalSemaphore in
ExternalVkImageGLRepresentation for synchronization with Vulkan
[150084:1:1005/102829.364500:ERROR:command_buffer_proxy_impl.cc(328)]
GPU state invalid after WaitForGetOffsetInRange.
[150234:1:1005/102829.382907:ERROR:command_buffer_proxy_impl.cc(125)]
ContextResult::kTransientFailure: Failed to send
GpuControl.CreateCommandBuffer.
[149735:149735:1005/102829.393012:ERROR:gpu_process_host.cc(956)]
GPU process exited unexpectedly: exit_code=133
[150295:150295:1005/102829.529107:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process
gpu-process.
[150295:150295:1005/102829.531704:ERROR:vulkan_device_queue.cc(217)]
Vulkan: AMD RADV RENOIR (ACO)
amdgpu: The CS has been rejected, see dmesg for more
information (-22).
[150295:150295:1005/102913.650278:ERROR:gles2_cmd_decoder_passthrough.cc(1547)]
GLES2DecoderPassthroughImpl: Context reset detected after
MakeCurrent.
[150295:150295:1005/102913.650922:ERROR:gpu_service_impl.cc(945)]
Exiting GPU process because some drivers can't recover from
errors. GPU process will restart shortly.
[150084:1:1005/102913.664169:ERROR:command_buffer_proxy_impl.cc(328)]
GPU state invalid after WaitForGetOffsetInRange.
[149735:149735:1005/102913.668666:ERROR:command_buffer_proxy_impl.cc(328)]
GPU state invalid after WaitForGetOffsetInRange.
[149735:149735:1005/102913.679697:ERROR:gpu_process_host.cc(956)]
GPU process exited unexpectedly: exit_code=8704
[150569:150569:1005/102913.785831:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process
gpu-process.
[150569:150569:1005/102913.787253:ERROR:vulkan_device_queue.cc(217)]
Vulkan: AMD RADV RENOIR (ACO)
..
and 'dmesg'
...
[Oct 5 10:29] [drm:amdgpu_syncobj_lookup_and_add_to_sync
[amdgpu]] *ERROR* syncobj 1834 failed to find fence @ 0 (-22)!
[ +0.000130] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed
in the dependencies handling -22!
All that tempts me to report a 'bug' but since there is no
'Chrome' in Bugzilla I thought I'd ask around here for
thoughts & opinions.
Google's map is in my case the most evident place where
Chrome struggles horribly, since the issues arose (I've
reset Chrome's settings to defaults too)
I think that system coming back from 'sleep' might have a
role in this - after reboot and until sleep I think Chrome
runs fine but cannot say I 'programmatically' verified this.
Right now I'm on 5.14.9-200.fc34.x86_64 and
google-chrome-stable-94.0.4606.71-1.x86_64 and in case
hardware matters, which it most likely does - I'm on Lenovo
e14 gen2 with AMD's 4500U.
many thanks, L.