Ryan Foster

Closing per above.

As Snap Camera no longer distributes or supports their desktop app, we will be closing this as not planned.

For those who can reproduce this, please: 1. Post a full OBS log file from a session where this occurs. 2. Confirm that the problem _is not present_ in OBS...

The common items in each log reported so far are: 1. Apple Mac system 2. Intel CPU 3. AMD GPU 4. OBS 28.0+ (or OBS 28.1+) If you are experiencing...

What I'd really like to confirm is: 1. Does this occur in OBS Studio 28.0.1? 2. Does this occur in OBS Studio 28.1.0-beta1? Specifically those versions. That would narrow down...

Please provide updated screenshots so that we can reevaluate this PR.

Here are updated "after" screenshots after applying the change locally:   

We think that the crash on resolution change was resolved with commit https://github.com/obsproject/obs-studio/commit/feda64e9c618ed217a6549f3457960a54ebef207, which is available as of OBS Studio 28.1.0. Another fix was committed as https://github.com/obsproject/obs-studio/commit/6693f3928831a69d73ae057405a918559e6d32de (technically a revert,...

This, or at least the bulk of crashes like this, is (probably) fixed by #10203, so I'm going to optimistically close this as fixed. Should be shipped in OBS Studio...

> In short, media objects don't free their resources after being closed, which is not a problem if you have a limited number of them but critical for massive setups....