Vivaldi fails to run with GPU acceleration

Vistaus

Since the latest snapshot, Vivaldi only shows a white screen after opening and the terminal output keeps spamming the following message endlessly:

[13384:13384:0614/201041.849899:ERROR:gpu_channel_manager.cc(810)] ContextResult::kFatalFailure: Failed to InitializeGrContext for SharedContextState
[13384:13384:0614/201041.849956:ERROR:shared_image_stub.cc(460)] SharedImageStub: unable to create context
[13384:13384:0614/201041.849988:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub
[13384:13384:0614/201041.850639:ERROR:shared_context_state.cc(348)] OOP raster support disabled: GrContext creation failed.
[13384:13384:0614/201041.850673:ERROR:gpu_channel_manager.cc(810)] ContextResult::kFatalFailure: Failed to InitializeGrContext for SharedContextState

Vivaldi starts fine if I start it with --disable-gpu, but then I get graphical tearing.

OS: Deepin 20.2 (based on Debian 10)
GPU: Intel 620 UHD
Environment: Xorg (X11)

How do I fix this?

RogerWilco

Out of curiosity: which flags would you typically enable to get hardware acceleration?

I'm aware of these flags:
#ignore-gpu-blocklist
#enable-gpu-rasterization
#enable-accelerated-video-decode

OS: Linux Mint 20.1 Cinnamon, 5.8.0-55-generic kernel, nvidia-driver-460, Vivaldi 4.0.2312.27 (Stable channel) stable (64-Bit)

It has become really bad playing all sorts of video in the browser. From certain 100% spikes on one core when e.g. opening a new video or tab to the horizontal tearing which you describe.

Sure, there's the FreeTube application, but there's more media content out there than just from Youtube.
I really do like Vivaldi for its feature richness, but when media playback is that heavily affected ... not the best user experience to phrase it diplomatically.

Vistaus

But I wasn't talking about video hardware acceleration, but hardware acceleration of the browser itself. And it only started happening after the latest snapshot.

Those flags are set to default.

RogerWilco

Well, I am under the impression that also basic scrolling has become worse. I'm running imwheel for the mouse wheel though, but that hasn't caused trouble in the past. One horizontal part of the screen doesn't move as fast up/down as another part. Tearing issues, to me, are kind of what vsync is intended to address, the scrolling issue, let me call it (roofing) shingle effect.

^^ Absolutely a clear case of 'pebkac' and I'm not shying away from admitting it.
The scrolling issue, which I referred to as " (roofing) shingle effect", was due to a setting in the nVidia driver which I had only meant to temporarily change while I was desktop recording and forgot to switch back (OpenGL Setting > Allow flipping)

This is the first section of what I get for vivaldi://gpu

Graphics Feature Status
Canvas: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Hardware accelerated
OpenGL: Enabled
Rasterization: Hardware accelerated on all pages
Skia Renderer: Enabled
Video Decode: Hardware accelerated
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

Vistaus

@rogerwilco But how does that help my issue? Can anyone from the Vivaldi team jump in? 'Cause Vivaldi is pretty unusable without hardware acceleration

Vistaus

@gwen-dragon said in Vivaldi fails to run with hardware acceleration:

@vistaus Does this command give better perfoarmance?
vivaldi --use-gl=desktop

It's not really about performance, it's about the latest snapshot not working at all with hardware acceleration enabled. Your command does nothing to change that.

npro

@vistaus post your vivaldi://gpu

mib2berlin

@vistaus
Hi, I gues why most user here are a bit confused is you are talking about hardware acceleration but there is only GPU acceleration.
This is for better drawing browser window and/or video performance.
If you disable it in Vivaldi only video performance change, nothing else.
Mostly after a Chromium update several GPU are kicked and not suppored anymore.
If you want to overwrite the limitation use #ignore-gpu-blocklist
If not get Vivaldi to start and disable HW acceleration, ready.
The name hardware acceleration is total misleading.

Cheers, mib

Vistaus

@mib2berlin Good point, thanks! I meant GPU acceleration. But even with the blocklist enabled, it still fails to start properly.

@Gwen-Dragon Nope, stable fails to run with GPU acceleration as well.

@npro That's not gonna help much, 'cause I can currently only start Vivaldi with --disable-gpu, so that page isn't going to show anything useful.

mib2berlin

@vistaus
Hi, can you may check with an actual Chromium or Chrome vwith the same or higher verion number.
It doesent help you much but you can see if it is a Vivaldi only problem.
I use Intel HD 520 at moment without issues, hm.

Cheers, mib

Vistaus

@mib2berlin said in Vivaldi fails to run with GPU acceleration:

@vistaus
Hi, can you may check with an actual Chromium or Chrome vwith the same or higher verion number.
It doesent help you much but you can see if it is a Vivaldi only problem.
I use Intel HD 520 at moment without issues, hm.

Cheers, mib

I just installed Chromium and it starts just fine with GPU acceleration enabled, so the issue definitely seems to be Vivaldi-specific.

npro

@vistaus said in Vivaldi fails to run with GPU acceleration:

@mib2berlin said in Vivaldi fails to run with GPU acceleration:

@vistaus
Hi, can you may check with an actual Chromium or Chrome vwith the same or higher verion number.
It doesent help you much but you can see if it is a Vivaldi only problem.
I use Intel HD 520 at moment without issues, hm.

Cheers, mib

I just installed Chromium and it starts just fine with GPU acceleration enabled, so the issue definitely seems to be Vivaldi-specific.

@mib2berlin said in Vivaldi fails to run with GPU acceleration:

with the same or higher verion number.

Vistaus

@npro I installed Chromium 91, so same.

RogerWilco

@vistaus said in Vivaldi fails to run with GPU acceleration:

@rogerwilco But how does that help my issue? Can anyone from the Vivaldi team jump in? 'Cause Vivaldi is pretty unusable without hardware acceleration

How does it help you assess the situation? How about other data points, such as another Debiad-based OS, nVidia driver used, output from vivaldi://gpu.

If you want to communicate with the devs, then maybe open a proper ticket, including your hardware specs, kernel & driver info, extensions installed in Vivaldi, said vivaldi://gpu output from your PC et al. I'd have my doubts that they'd be spending much time on the forum.

Anyway, good luck and success.

Regards
another user

Vistaus

@rogerwilco As I said in the OP, I'm using the Intel driver - I don't even have an nVidia card.

Also, as I pointed out: I can't reach vivaldi://gpu properly, so there's no way to post anything from that page. And as you can see, I already confirmed that the issue is not present in Chromium 91 (same version as Vivaldi is based on).

I cannot currently test another Debian-based OS, but I've been using Deepin for a long time now and this issue only started in the previous snapshot.

Vistaus

Just updated the snapshot and the issue is still present

Vistaus

Alright, so I reinstalled Deepin from scratch and installed a fresh install of Vivaldi Snapshot, but the issue is still not solved

What else could I try to solve this?

coronium

@gwen-dragon Yes, for me too - stable version (4.0.2312.33-1). It has many errors on run. Only main window opens without any content (with white background). Some of errors on run are:

Errors:
ERROR: 0:1: '
' : invalid version directive
ERROR: 0:3: 'out' : storage qualifier supported in GLSL ES 3.00 and above only
ERROR: 0:3: '' : No precision specified for (float)
ERROR: 0:5: 'flat' : Illegal use of reserved word

[19715:19715:0619/200800.288427:ERROR:shared_context_state.cc(73)] Skia shader compilation error
------------------------
#version 330

out vec4 sk_FragColor;
noperspective in vec4 vQuadEdge_Stage0;
noperspective in vec4 vinColor_Stage0;
void main() {
    vec4 outputColor_Stage0;
    outputColor_Stage0 = vinColor_Stage0;
    float edgeAlpha;
    vec2 duvdx = dFdx(vQuadEdge_Stage0.xy);
    vec2 duvdy = dFdy(vQuadEdge_Stage0.xy);
    if (vQuadEdge_Stage0.z > 0.0 && vQuadEdge_Stage0.w > 0.0) {
        edgeAlpha = min(min(vQuadEdge_Stage0.z, vQuadEdge_Stage0.w) + 0.5, 1.0);
    } else {
        vec2 gF = vec2((2.0 * vQuadEdge_Stage0.x) * duvdx.x - duvdx.y, (2.0 * vQuadEdge_Stage0.x) * duvdy.x - duvdy.y);
        edgeAlpha = vQuadEdge_Stage0.x * vQuadEdge_Stage0.x - vQuadEdge_Stage0.y;
        edgeAlpha = clamp(0.5 - edgeAlpha / length(gF), 0.0, 1.0);
    }
    vec4 outputCoverage_Stage0 = vec4(edgeAlpha);
    {
        sk_FragColor = outputColor_Stage0 * outputCoverage_Stage0;
    }
}

coronium

@coronium Well, I managed Vivaldi to properly open by removing Default folder... I still do not know what exactly happened...

luetage

@coronium Maybe your session got borked. I would backup the current Default folder, delete it and put in the old one. Then open the folder, remove session storage and try to start. Worth a shot.