OBS Studio 33.0.1 hotfix plugs crashes and deadlocks tied to Twitch and YouTube logins
A week after OBS 33.0's sweeping backend overhaul, the first point update repairs the stability regressions that surfaced when the new browser engine and plugin system went live.
OBS Studio 33.0.1 is out now. It hit the GitHub release page on October 29, just a week after the 33.0 stable drop, and its entire job is fixing what broke when 33.0 shipped. The headline fixes target something that drives a lot of streamers up the wall: crashing and deadlocking when you try to sign in to Twitch or YouTube.
In between, the OBS team rebuilt a fair amount of plumbing.
33.0 was not the release you'd spot at a glance. Its biggest change was a roughly two-year jump in the CEF browser engine, the Chromium-based piece OBS leans on for browser sources, overlays, and interactive docks. That move took it from build 127 to build 150. The team described it as backend work that "should be invisible to users," and asked anyone noticing weirdness to report it. Two years of browser engine in a single commit is rarely invisible, though.
The other major shift was quieter still. Plugin loading got a complete redesign: bundled modules moved into a new folder called core, while third-party plugins got a fresh install location. Legacy plugins still work from their old homes until at least OBS 34.0, expected around August 2027. After that, they won't load.
Think of 33.0.1 as the leak repair.
What 33.0.1 actually fixes
The patch contains seven changes, and nearly all of them trace back to the new browser engine or the new plugin system.
The ones that hurt the most are the login fixes. WizardCM patched three of them: a startup crash when logged into a service integration, a Twitch login crash, and a YouTube login deadlock. All three live in the obs-browser component.
There's a race condition too, where browser panels could end up with incorrectly sized content. prgmitchell fixed a memory leak in the image slideshow source, and FiniteSingularity sorted out plugins failing to load on Flatpak, a problem tied directly to the new plugin layout. Warchamp7 handled the last one, fixing a Plugin Manager that stopped prompting you to save after a change until you reopened the dialog.
Each fix points back to 33.0's overhaul, and each one bites a workflow a meaningful chunk of users actually rely on.
It's not a grab-bag of new features. There's nothing flashy here. But a login crash is exactly the kind of thing that leaves you staring at a black window seconds before you go live, so it's worth the fix. The memory leak is a slow burn you won't feel in a short stream but will feel over a six-hour broadcast. The Flatpak fix matters for Linux users who've lived in containers for years.
Head here to download the new release.
