Vivaldi is corrupted
-
Basically, this is what happens every time I open vivaldi
It happened suddenly after booting my PC and happens every time I open Vivaldi. Anyone knows why that's happening? I didn't try reinstalling it since I have multiple things that aren't synced/backed up and I don't want to lose them. -
@jumbomiku That looks like a graphics driver mismatch, or a GPU starting to break down.
-
@jumbomiku A Mesa update is the culprit, it breaks GPU acceleration. You need to quit Vivaldi, visit your profile and delete the GPUCache and ShaderCache directories. After a restart it should work again. If you can’t get this to work you can alternatively start Vivaldi with the
--disable-gpu
flag, but you won’t have acceleration then. -
Same here on fedora 38 and
--disable-gpu
work for now. -
@luetage Yep, updated it and it's fixed now
-
I'm using ArchLinux and Wayland with a 6600XT AMD GPU.
b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c1)
I'm having the same issue, and it is caused by Vivaldi not a "breakdown" in GPU in my case. Reverting back to a 3 month old version of Vivaldi works fine.
The above mentioned corruption appears to be related to canvases, for me it is 100% reproducible opening up a Grafana dashboard.
Using option "--ozone-platform=wayland" appears to fix the issue. This also seems to disable Vulkan when checking "chrome://gpu".
The latest month of Vivaldi updates has been a real roller coaster ride regarding graphics, artifacts, flickering, 2-5s delays in page render ... etc on webpages compared to the latest Chromium.
Switching to software rendering makes all the issues go away, but I'm not prepared to trade a full 4 cores of CPU power just to watch a 1080p video. The hardware encoding/decoding is absolutely critical.
That being said, these are probably Chromium issues under the hood, but it would be great if someone could take a look at it.
-
@mgillespie @jumbomiku are you guys using Wayland?
-
Here is the corruption I experienced ...
and
(the text was not corrupted, I just had to obfuscate it)
-
@nkukard I’m on AMD and Wayland and nuking the caches fixed the issue. But if your Vivaldi UI isn’t affected, you might have a different problem altogether.
-
@luetage more than likely a different issue then, the corruption occurs on dynamic HTML5 canvases not png/jpg/gif or similar image. The dynamic HTML5 canvas is not cached.