obsproject / obsproject/obs-studio

Process does not exit when OBS is running

Open
#7,676 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

28.0.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/9gtwgOD7ziok9DEm

OBS Studio Crash Log URL

No response

Expected Behavior

My games process exits properly.

Current Behavior

My games process does not exit properly

Steps to Reproduce
  1. Buy and Install Vintage Story - https://www.vintagestory.at/
  2. Start OBS configure game window capture, match VintageStory.exe
  3. Start Vintage Story
  4. Exit Vintage Story
  5. Game keeps running as an invisible process in the task manager
Anything else we should know?

Hello, gamedev here. I develop a PC game in C#/OpenGL with the OpenTK framework. Whenever OBS is launched (not even actively recording), exiting my game becomes impossible. It leaves behind a process in the task manager and the capture preview in OBS also becomes stuck. I'm on Windows 10 Pro and OBS 28.0.3 without any plugins, just the default installation. I tried multiple ways to exit the game (window.Exit(), Environment.Exit(0), Process.GetCurrentProcess().Kill();) but none seem to properly exit with OBS started.
Without OBS the game exits just fine. How can I debug this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked OBS Studio log and reproducing the behavior on Windows 10 with OBS 28.0.3, Vintage Story, and game window capture enabled. No source file or test is named; done would be identifying a reproducible cause for the lingering process and documenting or fixing it.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.