ungoogled-chromium: YouTube "Something went wrong. Refresh or try again later."

OS/Platform

Windows

Installed

OS/Platform’s package manager

Version

128.0.6613.84

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

Can’t play youtube videos

How to Reproduce?

Clicking on a youtube video

Actual behaviour

Whenever I click on a youtube video it will just be a black loading screen and it will say “Something went wrong. Refresh or try again later” after a while. However this only happens on a single one of my accounts, it will work fine signed out or on another account. But I have tried on other browsers and it works with the same account. I have tried disabling extensions and clearing cookies and updating chromium.

Expected behaviour

Play the video

Relevant log output

No response

Additional context

No response

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 8
  • Comments: 164 (22 by maintainers)

Commits related to this issue

Most upvoted comments

Quick fix without disabling WebGL in case you guys have UBlock installed:

www.youtube.com##+js(prevent-canvas, /webgl/)

Up to some months ago, there was a per-site webgl switch in the permissions (same with webrtc), we need this back.

For people who wants to disable WebGL only for YouTube. You can try this userscript in Tampermonkey:

// ==UserScript==
// @name         The workaround for YouTube loading/buffering problem in ungoogled-chromium
// @namespace    http://tampermonkey.net/
// @version      2025-02-27
// @description
// @author       Zeke Dou
// @match        https://www.youtube.com/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=youtube.com
// @grant        none
// ==/UserScript==
//
// What is this userscript trying to address?
// When playing a video, only a small part of the video loads, and the subsequent
// parts do not load afterward.

(function () {
  "use strict";

  const originalGetContext = HTMLCanvasElement.prototype.getContext;
  HTMLCanvasElement.prototype.getContext = function (contextType) {
    if (contextType === "webgl" || contextType === "webgl2") {
      console.log("WebGL is disabled by Tampermonkey");
      return null;
    }
    return originalGetContext.apply(this, arguments);
  };
})();

Edit: You don’t need this any more. The problem has been fixed in 133.0.6943.141

Can confirm replacing the empty WebGL strings with some data also works for me (playback seems to work for extended durations, and without any buffering). I replaced the empty strings with a generic renderer/vendor taken from Windows 10:

--- a/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc
+++ b/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc
@@ -3834,7 +3834,7 @@ ScriptValue WebGLRenderingContextBase::g
                          String(ContextGL()->GetString(GL_RENDERER))));
         }
         return WebGLAny(script_state,
-                        String(ContextGL()->GetString(GL_RENDERER)));
+                        String("ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver-5.0.0)"));
       }
       SynthesizeGLError(
           GL_INVALID_ENUM, "getParameter",
@@ -3848,8 +3848,7 @@ ScriptValue WebGLRenderingContextBase::g
               pname, IdentifiabilityBenignStringToken(
                          String(ContextGL()->GetString(GL_VENDOR))));
         }
-        return WebGLAny(script_state,
-                        String(ContextGL()->GetString(GL_VENDOR)));
+        return WebGLAny(script_state, String("Google Inc. (Google)"));
       }
       SynthesizeGLError(
           GL_INVALID_ENUM, "getParameter",

Incognito works for me on 133.0.6943.98 MacOS arm64 build. Regular window with/without logging in does not work. Clearing YouTube’s/Google’s cache does not fix it. Videos do not buffer past 19 seconds. I feel like the issue was triggered by some server-side change on YouTube’s side.

Confirming: disabling FedCm with launch parameter --disabled-features=FedCm as per pull request #3209 fixed issue for me, even when hardware acceleration is turned on on Windows.

Its the new Nvidia driver. Either rollback to the older version of it or sign out from the google and watch it without singing it. I dont know what did they changed but im using the older version of the nvidia driver.

Here’s another alternative option that doesn’t involve rebuilding the chromium binaries to patch them.

You can download the ScriptSafe extension. We don’t need this extension to run on all sites, so feel free to limit this extension to YouTube.com only.

Image

Next, go to the ScriptSafe extension options, We don’t need a majority of the features so turn them all off.

Image

We only want one thing - that’s the Block WebGL Fingerprinting option, which you should enable.

Image

And that’s it, you’re done! Youtube should work just fine without WebGL, while WebGL functionality is not compromised on other websites.

I think the nvidia thing is a seperate issue as this isn’t unique to them. If I had to guess I’d say it’s something on youtube’s end

My brother in Christ, they didnt say anything about nvidia so there no shot you can get out and type “I tHiNk iTs DifFErENt”. Youre telling us to update adblocker and the browser. Is this a forum from 2005? What is next? sfc scannow? Please either type something helpful or dont type anything at all. Do you think were dumb enough to not to disable every extension including ublock? PLEASE MAN

Version 133.0.6943.130 Youtube doesn’t buffer past 20 seconds.

Up to some months ago, there was a per-site webgl switch in the permissions (same with webrtc), we need this back.

The webgl patch was added way back in 2018 before the decision was made to have those changes be opt-in. I can set up a flag for that in 134.

@dumbmoron I’ve been testing using the generic swiftshader strings without issue. I think that change would make for a better default if you want to make a PR.

Yeah, for me enabling WebGL in chrome://flags seems to have fixed the problem. Thanks for the discussions everyone.

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

Could you please share your build?

Sure. But I am far from being a C++ developer, so I can’t vouch for the stability of the build =) I think I did everything according to the README instructions.

Here is the installer and zip archive with the distribution:

https://www.dropbox.com/scl/fo/tiwcg0ewvllwgb54mjli2/AIKWWHh2ASd7_kXWT0fQCC8?rlkey=t8cyhcp4x2bg8tgi2evl5x7o2&st=8fld0qio&dl=0

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

My disable-webgl-renderer-info.patch: Modified the patch file so that it does not make any changes

# Return blank values for WebGLDebugRendererInfo to remove a potential data
# leak while preventing potential website breakage
--- a/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc
+++ b/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc
@@ -3833,7 +3833,7 @@ ScriptValue WebGLRenderingContextBase::g
               pname, IdentifiabilityBenignStringToken(
                          String(ContextGL()->GetString(GL_RENDERER))));
         }
-        return WebGLAny(script_state,
-                        String(ContextGL()->GetString(GL_RENDERER)));
+        return WebGLAny(script_state,
+                        String(ContextGL()->GetString(GL_RENDERER)));
       }
       SynthesizeGLError(
           GL_INVALID_ENUM, "getParameter",
@@ -3847,7 +3847,7 @@ ScriptValue WebGLRenderingContextBase::g
               pname, IdentifiabilityBenignStringToken(
                          String(ContextGL()->GetString(GL_VENDOR))));
         }
-        return WebGLAny(script_state,
-                        String(ContextGL()->GetString(GL_VENDOR)));
+        return WebGLAny(script_state,
+                        String(ContextGL()->GetString(GL_VENDOR)));
       }
       SynthesizeGLError(
           GL_INVALID_ENUM, "getParameter",  

And what about the Mac version? Will it be fixed too?

See for yourself 😃 https://github.com/ungoogled-software/ungoogled-chromium-macos/actions/runs/13618617664

@li12138 Disable any adblocker like uBlock and uMatrix. Delete all cookies for Youtube site. Go to site, wait for cookie banner, click accept all or customize it. Re-enable adblocker. Then make sure WebGL is disabled, restart browser. Next version 133.0.6943.141 which is already out has the WebGL vendor string fixed.

macOS 15.3.1 brew 250226 up-to-date ungoogled-chromium 133.0.6943.98

symptoms: youtube videos produce spinner at 19 s or on timeline-click beyond 19 s

Disabling WebGL works: navigate to: chrome://flags/#disable-webgl Experiment: Disable WebGL: set pull-down on right to Enabled — browser restarts, youtube now works — does not lead to high cpu-load or 4K-video troubles

Some Web site charts and graphics will have blank areas

Apparently no proper fix for ungoogled-chromium for 6 months

Initially just logging out of my account fixed it, but videos started buffering again. I basically tried every suggestion here–outside of completely disabling hw-accel, removing cache/cookies/history, spoofing UA, changing profiles, removing uBlock, adding launch parameters didn’t seem have an effect. Happy to confirm disabling WebGL in chrome://flags does the trick for me!

It does not make sense that disabling hardware acceleration would fix this problem:

  • for the first 19 seconds video is playing fine
  • problem fixes itself switching to another account (but inconvenient)

And it does not fix problem for me

ps: i would recommend to avoid using ungoogled-chromium since binaries are being build god know by whom and with what patches or intents.

when i disable hardware acceleration its work , maybe some patch that has something to do with hardware acceleration that cause this

@Felpopos @Zeldaboy14 There were reports of it working fine with another google account, so it is more likely that usage of ungoogled-chromium with the specific google account to blame.

Have the same issue since yeasterday. I’m using version 122 on Win 10 with ublock origin and tampermonkey + enhancer for youtube. Seems like youtube changed something, because until 20.02.2025 i had no problems with it on ungoogled chromium. Suddenly I reseted browser to check if it help but it didnt.

Rejecting cookies breaks playback anywhere above first 2-5s. I can watch YT normally only if I accept all cookies from incognito mode or when not signed in. When I sign in it always breaks… on my main account. Switching account to a burner makes YT work again, but switching back to main YT account reveals that its still broken.

Disabling Hardware Acceleration seems to allow the player to play on any account (including non-logged in) no matter if cookies were accepted or not.

It would seem that clearing cookies doesnt help because your choices MIGHT be stored on google’s/YT side. I was unable to find anything regarding it from any of google’s and youtube’s account management tools. And to make matters worse - google chrome doesnt seem to have this problem.

Works again for me too yay 😃

Thanks for the support!! Seems to have resolved itself

@vvhitevvizard Do you have 403 errors in DevTools when it works while you’re logged-in without hw acceleration?

I cannot test now b/c the status changed. Today, I reverted HW accelleration setting back to Enabled and wow! YT works again (signed and with uBlock and all my extensions enabled). The only changes I made since yday was updating some system device drivers (excluding video card) for my laptop (Lenovo TB 14 IRL).

@Chricky Veeeeery soon: https://github.com/ungoogled-software/ungoogled-chromium-windows/actions/runs/13602234090

Just installed that version, works like a charm so far! WebGL and hardware Acc still active and tampermonkey de-activated ❤️

It might be a good idea wait and to see how much of an impact that change has for most people. At least for me the new gl string makes the FedCm flag unnecessary.

It has broken yet again. can’t load past 20 seconds

Just yet another workaround, but I’ve found out that if you use embedded URLs, e.g. https://www.youtube.com/embed/videoid instead of https://www.youtube.com/watch?v=videoid, then videos also play with no issues…

So, if I understand correctly, so far :

  • Disabling WebGL is a temporary fix, with some adverse consequences on other websites apparently ?
  • Windows users can use a different build without a specific patch to work around the issue
  • #3217 would most likely fix the issue for everyone and still prevent fingerprinting through WebGL

Thank you for this discussion! I’d been trying everything for hours but nothing worked. I don’t block ads. Multiple reboots. Works fine in other browsers and official YT mobile app (even logged in, which rules out account issue). Tried with/without third party cookies and with/without hardware acceleration. Vanilla Google Chrome worked.

On ungoogled-chromium, went to chrome://flags and enabling the “Disable WebGL” and relaunching it worked immediately. I’m using 133.0.6943.130 ungoogled-chromium (Marmaduke’s build) from https://chromium.woolyss.com/

On a side note @tomasz1986 :

ps: i would recommend to avoid using ungoogled-chromium since binaries are being build god know by whom and with what patches or intents.

That is true if you’re using crlauncher or any other source. With the only exception being you follow the README:

chrlauncher uses macchrome/winchrome/releases is it not trustworthy?

It is not. For one, there is no source code available, so you have to trust the person doing the compilation that they rely on the actual unmodified Ungoogled Chromium source (which is a no-go in terms of security).

The only official Windows releases are available at https://github.com/ungoogled-software/ungoogled-chromium-windows/releases. They are built via GitHub Actions, so anyone can check and inspect the whole build process.

Dude, thank you for this link. I’ve been using Marmaduke’s compilation (with gratitude to Marmaduke btw!) from that Woolyss website with Chromium Launcher for years now since at the time I couldn’t find an official exe build for Windows. I’ll try to migrate to the binaries from that repo, assuming they are more official and traceable to the source.

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

Could you please share your build?

Sure. But I am far from being a C++ developer, so I can’t vouch for the stability of the build =) I think I did everything according to the README instructions.

Here is the installer and zip archive with the distribution:

https://www.dropbox.com/scl/fo/tiwcg0ewvllwgb54mjli2/AIKWWHh2ASd7_kXWT0fQCC8?rlkey=t8cyhcp4x2bg8tgi2evl5x7o2&st=8fld0qio&dl=0

Thank you very much! It is working perfectly for me on WIndows 10!

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

My disable-webgl-renderer-info.patch: Modified the patch file so that it does not make any changes

By the way, just for information, Ublock Origin and SponsorBlock are installed. It does not interfere with YouTube. Videos load normally with these extensions and hardware acceleration enabled.

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

My disable-webgl-renderer-info.patch: Modified the patch file so that it does not make any changes

Return blank values for WebGLDebugRendererInfo to remove a potential data

leak while preventing potential website breakage

— a/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc +++ b/third_party/blink/renderer/modules/webgl/webgl_rendering_context_base.cc @@ -3833,7 +3833,7 @@ ScriptValue WebGLRenderingContextBase::g pname, IdentifiabilityBenignStringToken( String(ContextGL()->GetString(GL_RENDERER)))); }

  •    return WebGLAny(script_state,
    
  •                    String(ContextGL()->GetString(GL_RENDERER)));
    
  •    return WebGLAny(script_state,
    
  •                    String(ContextGL()->GetString(GL_RENDERER)));
     }
     SynthesizeGLError(
         GL_INVALID_ENUM, "getParameter",
    

@@ -3847,7 +3847,7 @@ ScriptValue WebGLRenderingContextBase::g pname, IdentifiabilityBenignStringToken( String(ContextGL()->GetString(GL_VENDOR)))); }

  •    return WebGLAny(script_state,
    
  •                    String(ContextGL()->GetString(GL_VENDOR)));
    
  •    return WebGLAny(script_state,
    
  •                    String(ContextGL()->GetString(GL_VENDOR)));
     }
     SynthesizeGLError(
         GL_INVALID_ENUM, "getParameter",
    

thats great , can confirm that disable webgl on chrome://flags did fix the issue

Confirming: disabling FedCm with launch parameter --disabled-features=FedCm as per pull request #3209 fixed issue for me, even when hardware acceleration is turned on on Windows.

Window wise for those having problems still I was able to get this to work by adding the flag, relogging in and disabling hardware acceleration via Menu > Settings > System. All this together and things seem to be working again!

Can confirm I am getting the same issue as others, specifically my main Youtube account is not able to play videos past the 20 second mark on Ungoogled Chromium, regardless of cookies or extensions. Using other accounts, or my main account with other browsers works. Just glad it’s not something I messed up, hopefully we can figure this out soon.

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Additional info from another issue:

Signing into any other account resolves the issue

All that even without changing the browser and profile, right? That is, you do not experience this issue with another account but with the same ungoogled-chromium, right? Correct same browser. With ad-blocker enabled and don’t have to clear browser cache or anything before signing into different account and it resolves the issue. Very strange have been searching the web for people with similar issues but can’t find anything conclusive around people having issues that they’ve traced back to their account.

Originally posted by @Coregod360 in #3097

Switching to another youtube account or disabling hardware acceleration helps me

Originally posted by @deonix37 in #3097

This behavior seems to have changed in the past week. I can now no longer watch videos when signed in into any account. Incognito with cookies rejected still works. Additionally having adblock enabled when incognito seems to also break video playback now.

I still blame Youtube, Another thing i noticed is that Youtube shorts always work so it seems like the thing they use to break video playback hasn’t been propograted to their shorts player ( i don’t think you can ads there so it makes sense )

Yep, started to work for me too. I think the main reason - google itself and this problem can appear at any time soon again.

Working for me on Linux with 126.0.6478.126 as of today - logged in, ublock, etc.

I tested today on 129.0.6668.96, after a few days of running Firefox. No problem loading anymore.

The person who opened this issue is facing the same issue I was somehow able to resolve. Me suggesting the steps I took doesn’t invalidate whatever issues you’re having and there’s no reason to get offended just because someone differentiates the two.

So weird. We have the same issue but youre claiming that “you somehow able to resolve”. Its been a week my dude. Youre method is 2005 windows forum methods that are insanely… never mind. I solved my issue by installing older version of nvidia driver, i have no problem. Can you use your brain? Offended? Theres a difference between offended and mad. Im mad because you dont know anything about anything and youre telling us to update ublock. lol

can’t they just make webgl not clear info. this fixed the youtube issue

https://github.com/ungoogled-software/ungoogled-chromium/commit/3c764bfc0bddd5897724e2c93e87c8d68420858f

Flatpak UG has used VAAPI for as long as I can remember, unless I’m misunderstanding. The main test I recall for vaapi was going to a site like YouTube, playing a video, and seeing what codec is used in chrome://media-internals/. There was a list of some that meant if you were or were not. When having the right hardware accelerated features listed in about:gpu, I would always have the right codecs being used in chrome://media-internals/.

No, an ultimate test/validation - in my mind - is, while playing a video, say YT, do: a) Open Devloper tools b) Ctrl + Shift + P c) Type “media” d) in the left pane find currently played string e) right pane should show something as my screenshot and “a must” are: Decoder Name & Hardware decoder

Image

And what about the Mac version? Will it be fixed too?

See for yourself 😃 https://github.com/ungoogled-software/ungoogled-chromium-macos/actions/runs/13618617664

What I’ve tried during the day is still working. Thanks

While the problem is fixed in 133.0.6943.141, it seems like the solution will soon change to be opt-in according to #3221.

Edit: I’ve misunderstood the change.

The problem was only caused by returning a blank string. These changes will return the real strings without the flag and the spoofed strings when the flag is enabled. Both states will work.

So YT should continue to work without intervention in M134 but the browser may start exposing more system data.

To re-enable the fix in M134: To restore the same behavior as 133.0.6943.141:

  • per profile, with chrome://flags/#spoof-webgl-info
  • globally, launching with --enable-features=SpoofWebGLInfo

Fork of block webgl on youtube and added h264ify to change the codec of the videos to h264 and decrease cpu usage.

// @name         YouTube Workaround and H264ify
// @version      2025-02-27
// @description  Combines the workaround for YouTube loading/buffering problem in ungoogled-chromium with H264ify for YouTube.
// @author       Zeke Dou
// @match        https://www.youtube.com/*
// @match        *://*.youtube.com/*
// @match        *://*.youtube-nocookie.com/*
// @match        *://*.youtu.be/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=youtube.com
// @grant        none
// @run-at       document-start
// ==/UserScript==
(function () {
    "use strict";
    
    const h264ifyEnable = true;
    const h264ifyBlock60fps = false;
    
    const originalGetContext = HTMLCanvasElement.prototype.getContext;
    HTMLCanvasElement.prototype.getContext = function (contextType) {
        if (contextType === "webgl" || contextType === "webgl2") {
            console.log("WebGL is disabled by Tampermonkey");
            return null;
        }
        return originalGetContext.apply(this, arguments);
    };
    
    if (!h264ifyEnable) {
        return;
    }
    
    function override() {
        var videoElem = document.createElement('video');
        var origCanPlayType = videoElem.canPlayType.bind(videoElem);
        videoElem.__proto__.canPlayType = makeModifiedTypeChecker(origCanPlayType);
        
        var mse = window.MediaSource;
        if (mse === undefined) return;
        var origIsTypeSupported = mse.isTypeSupported.bind(mse);
        mse.isTypeSupported = makeModifiedTypeChecker(origIsTypeSupported);
    }
    
    function makeModifiedTypeChecker(origChecker) {
        return function (type) {
            if (!type) return '';
            
            var disallowed_types = ['webm', 'vp8', 'vp9', 'av01'];
            for (var i = 0; i < disallowed_types.length; i++) {
                if (type.includes(disallowed_types[i])) return '';
            }
            
            if (h264ifyBlock60fps) {
                var match = /framerate=(\d+)/.exec(type);
                if (match && parseInt(match[1], 10) > 30) return '';
            }
            
            return origChecker(type);
        };
    }
    
    override();
})();```

@Chricky Veeeeery soon: https://github.com/ungoogled-software/ungoogled-chromium-windows/actions/runs/13602234090

And what about the Mac version? Will it be fixed too?

Fixed for me in 133.0.6943.141 - and it definitely wasn’t NVIDIA-related since I had the issue and don’t have NVIDIA. Couldn’t watch video YT videos (couldn’t skip around, sometimes they’d play until 19s in).

I do not have any Google account, and have never logged in. But I have been hit with the problem a few months ago (cookie clearing helped) and then a few days ago (cookie clearing no longer helpful). Or did I misunderstand? Thanks.

@bsdice That’s another datapoint, I had an impression that this issue never happens should you never log in.

@gopherit @lejeczek Thanks for confirming that the issue is fixed in .146!

Long thread, but after disabling WebGL around February 25 (which worked), updated to 133.0.6943.146 recently. Re-enabled WebGL and re-launched Chromium and everything is normal. So FYI disabling WebGL is a reliable workaround (and disabling FedCM?), but things are now back to normal as of .146 so the workaround is no longer needed.

Я полагаюсь на более старую сборку Ungoogled-Chromium по причинам доступности

Проблема на YouTube может быть отслежена до этого патча с 2018 года: F71C203, поэтому я не совсем понимаю, как вы не могли бы столкнуться с этой конкретной проблемой с тех пор, как YouTube не принес его в яркий солнечный свет.

Помимо, пожалуйста, изучите длинную серию эксплойтов для любой версии хрома. Что-то противное и эксплуатируемое выходит каждые 2-4 недели. Это бесконечно и никогда не закончится, потому что код-это один горячий беспорядок во многих местах. Я бы никогда не порекомендовал запустить какой-либо старый Ungoogled-Cromium. Вы поймаете что -то, рано или поздно, даже с Ublock и Umatrix или Pihole DNS. Может быть, лучше попробовать поддерживаемую вилку Firefox, как, по общему признанию, самоуверенный Палун, также с Ublock.

Или, если это для некоторого сайта Fringe, сообщите им об ошибке, так что это может быть исправлено с их конца.

Disabled WebGL… and it works! Kinda disappointed with this browser. Might switch to Firefox.

I rely on an older build of ungoogled-chromium for accessibility reasons

The Youtube problem can be traced to this patch from 2018: https://github.com/ungoogled-software/ungoogled-chromium/commit/f71c203e02577bf351750ca76d06d36fedc4fc69 So I don’t quite grasp how you could not have hit this particular problem since, until Youtube brought it into bright sunlight.

Aside, please research the long string of exploits for any chromium version. Something nasty and exploitable is coming out every 2-4 weeks. It is never-ending and will never end, because the code is one hot mess in alot of places. I would never recommend to run any older ungoogled-chromium. You will catch something, sooner or later, even with uBlock and uMatrix or a Pihole DNS. It may be better to try a maintained Firefox fork like the admittedly opinionated Palemoon, also with uBlock.

Or if this is for some fringe website, report a bug to them, so it can be fixed at their end.

is it possible to set the string from this patch 3c764bf with launch parameters

@borkfomb No, but you can give --disabled-features=FedCm a try.

multiple different issues involved

@Ahrotahn Perhaps it is worth re-submitting your fix for fed-thing since disabling it helped in a number of cases?

This was automatically closed via #3217, but there’s likely multiple different issues involved so we’ll keep this open for now.

I can confirm this was triggered by a change on the YouTube side, I also noticed some pre-roll ads are managing to bypass UBlock on an older setup.

FWIW https://music.youtube.com is not affected by this and works with WebGL enabled.

Yes it works by deactivating the webgl but the problem is that now I cannot play my favorite online games there will be no other solution without having to touch the webgl

Perhaps Youtube does not like that ungoogled-chromium clears WebGL info? Could someone build ungoogled-chromium without this patch and test again?

Thank! It worked for me. Hardware acceleration is enabled. Windows 11, version 133.0.6943.126.

Could you please share your build?

Sure. But I am far from being a C++ developer, so I can’t vouch for the stability of the build =) I think I did everything according to the README instructions.

Here is the installer and zip archive with the distribution:

https://www.dropbox.com/scl/fo/tiwcg0ewvllwgb54mjli2/AIKWWHh2ASd7_kXWT0fQCC8?rlkey=t8cyhcp4x2bg8tgi2evl5x7o2&st=8fld0qio&dl=0

I’ve got the same issue on Youtube with official build 133.0.6943.126, and his build resolved it. Thank you. Neither uBlock Origin nor privacy DNS blocklists weren’t the cause.

Image

Enable “Disabled WebGL” in chrome://flags work for me, thanks everyone for the dicussion!

Can confirm this, but I’m using sites that are dependent on WebGL, so that’s no option for me…

You don’t have to turn off WebGL, you can use a build without the patch that clean the webgl info. I gave a link above to the Windows build.

https://www.dropbox.com/scl/fo/tiwcg0ewvllwgb54mjli2/AIKWWHh2ASd7_kXWT0fQCC8?rlkey=t8cyhcp4x2bg8tgi2evl5x7o2&st=8fld0qio&dl=0

Or you can make a new build with the patch edits from dumbmoron from the issue above.

Confirming: disabling FedCm with launch parameter --disabled-features=FedCm as per pull request #3209 fixed issue for me, even when hardware acceleration is turned on on Windows.

Tried this, no luck for me. However, when not signed in or in an incognito window YT works.

ps: i would recommend to avoid using ungoogled-chromium since binaries are being build god know by whom and with what patches or intents.

That is true if you’re using crlauncher or any other source. With the only exception being you follow the README:

chrlauncher uses macchrome/winchrome/releases is it not trustworthy?

It is not. For one, there is no source code available, so you have to trust the person doing the compilation that they rely on the actual unmodified Ungoogled Chromium source (which is a no-go in terms of security).

The only official Windows releases are available at https://github.com/ungoogled-software/ungoogled-chromium-windows/releases. They are built via GitHub Actions, so anyone can check and inspect the whole build process.

ps: i would recommend to avoid using ungoogled-chromium since binaries are being build god know by whom and with what patches or intents.

That is true if you’re using crlauncher or any other source. With the only exception being you follow the README: https://github.com/ungoogled-software/ungoogled-chromium#:~:text=Reporting%2C Contacting.-,Downloads,These binaries are known as contributor binaries.,-Source Code

Broke for me this morning but signing out of my account fixed it. weird. Edit: reddit thread on ublock has a bunch of people(firefox, normal chrome users) talking about it. I’m thinking it’s related to google phasing out manifest v2 or some type of integrity/attestation failure. 😞

Heisenbug it seems 😃

@vvhitevvizard Do you have 403 errors in DevTools when it works while you’re logged-in without hw acceleration?

I have the same issue. It started since October I think. It shows YT video for ~20 secs and then yields the same “unexpected error”. I tried with the latest 129 and with old 115 version, with all the extensions disabled. Nothing helps. NVidia driver does not matter. I have Intel Iris Xe iGPU (13700H) laptop. But if I log out then YT video works.

EDIT: Disabling hardware acceleration WORKS. But power efficiency is worse and I get a lot of dropped frames.

Tried using a hotspot from my phone already. Doesn’t work either

@leolurch Please try with mobile data, would it be any better?

to everyone: my question still stays: Did anyone have QUICK enabled?

It fixed itself automatically today, without trying anything new.

Its the new Nvidia driver. Either rollback to the older version of it or sign out from the google and watch it without singing it. I dont know what did they changed but im using the older version of the nvidia driver.

My brother in Christ, they didnt say anything about nvidia so there no shot you can get out and type “I tHiNk iTs DifFErENt”. Youre telling us to update adblocker and the browser. Is this a forum from 2005? What is next? sfc scannow? Please either type something helpful or dont type anything at all. Do you think were dumb enough to not to disable every extension including ublock? PLEASE MAN

The person who opened this issue is facing the same issue I was somehow able to resolve. Me suggesting the steps I took doesn’t invalidate whatever issues you’re having and there’s no reason to get offended just because someone differentiates the two.