[Opera 28] ''GPU Process Was Unable To Boot''
-
l33t4opera last edited byHi @joegd21, go to the address bar, and type opera:flags#ignore-gpu-blacklist, press Enter, and click "Enable" button, restart the Opera, and see if this helps
-
joegd21 last edited by
Thanks for your replies, guys.
@Lando242, I did a clean install, but that didn't work. I checked the option ''Delete my Opera user data'' in the uninstaller and went to the profile directory to make sure the folder was deleted (and yes, it was).
@L33t4opera, I already have that flag enabled. It was working before the update, now it has no effect.
My guess is that something is preventing the GPU process to be launched on Opera's startup. As I said: only Opera 28 and 29 are affected (for now), so I assume that it's some kind of unidentified bug inside the browser's code. That would explain why the flag doesn't work and why the GPU process is not listed under the task manager.
-
joegd21 last edited by
Today is 10/16/2015. The problem hasn't been solved yet. The browser's GPU process is not working since version 28 and it seems there's no solution for this. Chrome is the only Chromium-based browser in which hardware acceleration is working for me.
-
-
joegd21 last edited by
I've cleared all browsing data (History, Cache, Cookies...) several times and that hasn't solved the problem. Something is preventing the GPU process from booting during the startup. I'd be happy if I could find a workaround.
-
sfearmentor last edited by
I had the same problem with Intel GMA 3150 (Windows 7 Ultimate, 32-bit). What is even worse is that Opera is not using the proprietary system codecs (like H.264 and MP3) if the GPU process is not running. I managed to find a workaround, though. According to opera:gpu the troublemaker is the EGL.
Copy "d3dcompiler_46.dll", "libEGL.dll" and "libGLESv2.dll" from the installation folder of v27 to the installation folder of the newer version ("libEGL.dll" and "libGLESv2.dll" will prompt for overwrite so rename them). Instead of copying "d3dcompiler_46.dll" from v27 you can also rename the newer version's "d3dcompiler_47.dll" to "d3dcompiler_46.dll".
I'm using v31.0.1889.99 and this enables hardware acceleration for me. No unexpected behaviour or crashes. I hope it will work for you as well, joegd21.
-
joegd21 last edited by
Thanks! It worked (partially). Most of the features listed are hardware accelerated now, but for some reason, WebGL isn't working :awww: . However, I used the same method with Chrome (which had been having the same problem since the update to v46) and it worked flawlessly. Now I know where the problem comes from .
-
sfearmentor last edited by
You are welcome!
WebGL has never worked for me, neither in v27 nor in any other version I have tried. Did it for you? I saw Intel GMA 3150 is blacklisted:
Intel Graphics Media Accelerator 3150 causes the GPU process to hang running WebGL: 305431
Disabled Features: webgl
and enabling "Override software rendering list" didn't help. I didn't bother anymore, because it wasn't crucial for me. Now that you said, I tried Chrome, it states the same thing as above, but WebGL works, which is strange. I'll investigate further. Does opera:gpu state anything considering the Express chipset? -
joegd21 last edited by
Nothing regarding the Express Chipset. It says something about the driver version, but it's not related to WebGL.
Here's what it says: ''Accelerated video decode interferes with GPU sandbox on older Intel drivers''.There are no new updates for the driver and I don't care about the hardware-accelerated video decode, but it seems that WebGL is supposed to work for me and it isn't. BTW, I'm still experiencing problems with proprietary media codecs.
-
sfearmentor last edited by
Hm, that's strange. What I have found so far is that (in my case) Chrome is using SwiftShader for GL rendering. I think it's falling back to it if there is a problem with the ANGLE renderer (those DLLs we moved). SwiftShader is completely software based, that's why WebGL is working for me in Chrome. If I rename the folder (C:\Users\*\AppData\Local\Google\Chrome\User Data\SwiftShader) so Chrome can't use it, ANGLE is used and I get the same situation as in Opera. I used it with Opera, but unfortunately the whole browser is laggy, glitchy and there is this huge SwiftShader watermark. WebGL works, though. I was almost sure it was the Intel GPUs, but you say yours is not blacklisted...
Anyway, what's with the codecs? They generally do not work or just some specific files you've came across? -
joegd21 last edited by
Anyway, what's with the codecs? They generally do not work or just some specific files you've came across?
They just won't work, no matter the page I visit. Wherever there's an embedded mp3 or h.264 file, I cannot play it. I've already created a thread about it, but I could't find a solution.
-
l33t4opera last edited by
but it seems that WebGL is supposed to work for me
Hi @joegd21, you can try to add the
--disable-gpu-sandboxswitch at the end of the shortcut to thelauncher.exe, as follows:"path\to\the\launcher.exe" --disable-gpu-sandbox, and see if this helps
