Well, it’s complicated.
It seems like Chrome started using the Vulkan backend if available (since about 107) and in the case of an Intel iGPU this seems to be broken. The root cause would then be a faulty Intel driver… or its integration which would then be Google turf again.
