Skip to content

Zombie process when using multiple OBS instances with browser sources #11658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MatinAniss opened this issue Dec 22, 2024 · 2 comments · Fixed by #11977
Closed

Zombie process when using multiple OBS instances with browser sources #11658

MatinAniss opened this issue Dec 22, 2024 · 2 comments · Fixed by #11977

Comments

@MatinAniss
Copy link

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

31.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/VJcgBgDLaBUFBGro

OBS Studio Crash Log URL

No response

Expected Behavior

Browser sources to work in more than one OBS instance and no zombie processes after closing all OBS instances.

Current Behavior

Browser sources not working on more than one OBS instance (the original instance remains to work but additional instances do not), then when closing all OBS instances a remaining zombie process is left in the background OBS Studio which can be seen in Task Manager.

Steps to Reproduce

  1. Open OBS
  2. Create a scene with at least one browser source.
  3. Open another OBS instance.
  4. Observe browser source not working in new instance.
  5. Close all instances of OBS.
  6. Observe zombie process that should have been ended OBS Studio in Task Manager.

Anything else we should know?

This issue seems to only happen when using at least one browser source.

@mantran4
Copy link

+1

@invalidtask
Copy link
Contributor

+1 this issue.

Same issue happening across multiple PCs. If you use more than one OBS instance, only the first instance will load OBS Browser sources. The other instances do not. They also do not generate any warnings or errors in the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants