Glitchy display after a short while
-
Well, I haven't even know about
vivaldi://flags
So I have everything default there. I've only made a couple of changes via the settings UI and added a couple of extensions and that's it.For now, without hardware acceleration it seems to be working ok...
-
@wojtek Thanks. Looks like there may be an incompatibility between the Chromium GPU acceleration code and a new graphics driver in High Sierra.
If you should need to re-enable hardware acceleration, the one other thing you can do is to check
vivaldi://gpu
to see if any problems get reported there. -
I've re-enabled hardware acceleration a while back with the desire to catch some logs, but
vivaldi://gpu
only shows a lot of:Log Messages [34736:775:1001/172348.742348:INFO:propmedia_gpu_channel.cc(99)] : PROPMEDIA(GPU) : AllowHardwareDecode : Hardware Decode Not Enabled [34736:775:1001/172350.296262:INFO:propmedia_gpu_channel.cc(99)] : PROPMEDIA(GPU) : AllowHardwareDecode : Hardware Decode Not Enabled [34736:775:1001/172353.435981:INFO:propmedia_gpu_channel.cc(99)] : PROPMEDIA(GPU) : AllowHardwareDecode : Hardware Decode Not Enabled [34736:775:1001/172356.854471:INFO:propmedia_gpu_channel.cc(99)] : PROPMEDIA(GPU) : AllowHardwareDecode : Hardware Decode Not Enabled [34736:775:1001/172401.625805:INFO:propmedia_gpu_channel.cc(99)] : PROPMEDIA(GPU) : AllowHardwareDecode : Hardware Decode Not Enabled
-
OK, so in the end I went back to 1.12 stable. Being on beta doesn't bring that much benefit and on stable everything works just fine... (also - video playback wasn't working on some videos without acceleration)
-
@wojtek Could you please report this as a bug and a potential regression?
https://vivaldi.com/bugreport/
Vivaldi 1.12 (Stable) and Vivaldi 1.13 (Snapshot) are currently based on the same Chromium code so this glitch was likely (directly or indirectly) caused by a change in Vivaldi's code.
Thanks.
-
@xyzzy said in Glitchy display after a short while:
@wojtek Could you please report this as a bug and a potential regression?
https://vivaldi.com/bugreport/
Vivaldi 1.12 (Stable) and Vivaldi 1.13 (Snapshot) are currently based on the same Chromium code so this glitch was likely (directly or indirectly) caused by a change in Vivaldi's code.
Thanks.
Reported
FUN! Obviously after reporting it the problem started with 1.12 as well... FML (or rather 'beloved' chromium...)
-
@wojtek Have you tried disabling all extensions and then selectively re-enabling them?
Sometimes just disabling an extension is not enough. I would delete any extensions that could affect/customize/break Vivaldi's web-based UI.
Popular/well-tested extensions like uBlock Origin should not be contributing to your display glitches.
-
Well, I just experienced something similar in Fx, and after a quick chat with a friend (owning same MBP model) it turned out that sometimes he has similar display problems in Safari after upgrading to HS... I would guess there is some problem with HS and hardware acceleration..
-
@wojtek Thanks for the update. Hopefully it's just a software glitch that will be fixed soon.
-
I run into information that this may be related to the introduction of Metal 2... fingers crossed that they will fix that soonish...
-
Hi all,
I also have the same problem on macOS High Sierra. The frontend becomes very glitchy after a while with some flicker. OP mentions a friend owning the same MBP model - maybe that really happens only on that specific model? I'm using a 15'' MBP Early 2012. (I haven't experienced this behavior on Chrome so far.)
Cheers
Norman -
For now I'm running with hardware acceleration off and the problem seems to be gone (the side effect is that I can't play some YT videos...)
-
FYI, as I suspected, the updated drivers in High Sierra are indeed causing some rendering issues in Chromium-based browsers.
-
From the chromium report, this seems to only impact devices with nvidia graphics.
-
@rsaeks That's just for this particular bug. I didn't attempt to track them all down.
Hopefully these issues will be fixed soon for all those that are affected.
-
-