obsproject / obsproject/obs-studio

OBS crashing - logic bug?

Open
#11,034 0 comments 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

30.2.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/HQB7G8OiT10fy4hs

OBS Studio Crash Log URL

No response

Expected Behavior

I expected to be able to stream without fear of OBS crashing.

Current Behavior

OBS crashes sort of randomly.

Steps to Reproduce
  1. Start streaming
  2. Maybe OBS crashes, maybe it doesn't.
Anything else we should know?

This is a relatively new problem for me, starting around the end of May iirc. There doesn't seem to be a definite action that causes the crashes, though they sometimes seem to coincide with a Twitch alert. I posted on the OBS Discord asking for help and some troubleshooting advice I've gotten was to stop using stinger transitions, stop using scripts, stop using plugins, reinstall the VC redists, and so far I still crash.

The only changes I've made since the crash log I'm posting with this form are that I fully uninstalled + reinstalled the redists whereas before I just clicked "repair," and I also uninstalled a plugin that I started using in May.

I'm posting here because another user on the OBS forums (https://obsproject.com/forum/threads/obs-crashing-unsure-of-the-cause-stinger-transitions.176811/post-653179) suggested that it be posted here because they said something goes wrong with the pointers and memory and that it might be an OBS logic bug.

Thank you in advance for your time and please let me know if you need anything else from me. :)

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 OBS Studio log at https://obsproject.com/logs/HQB7G8OiT10fy4hs, focusing on the streaming period and any correlation with Twitch alerts. Reproduce the crash if possible and use additional crash data or a reliable reproduction to identify the failing component before defining a fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.