I am currently experiencing the same issue and went hunting for the solution today.
Now, I'm not saying this is the fix as I just applied it and am currently testing as I type this - but I think it might have to do with the added HW acceleration to the browser source, which was updated in OBS version 22 [along with other changes that happened to the browser source on that same build].
From the notes...
Major improvements to the browser source:
- Added hardware acceleration to the browser source on Windows for greatly improved performance, reduced resources, and allowing advanced rendering functionality such as WebGL. This reduces CPU usage, reduces RAM usage, and even reduces GPU usage. This option is enabled by default; it can be disabled in the advanced section of settings if needed if there are any unexpected issues.
I'll be testing it with that option disabled until tomorrow, so I'll keep you posted if this actually fixes it. =D
