obsproject / obsproject/obs-studio

OBS randomly crashes with "X Error of failed request: BadWindow (invalid Window parameter)"

Open
#12,027 2 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

Other

Other OS

Arch Linux

OBS Studio Version

Other

OBS Studio Version (Other)

31.0.2

OBS Studio Log URL

https://obsproject.com/logs/XNHx4bSOM7rW1K46

OBS Studio Crash Log URL

No response

Expected Behavior

OBS runs fine

Current Behavior

After a while, OBS will just crash with

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Resource id in failed request:  0x7400006
  Serial number of failed request:  1391548
  Current serial number in output stream:  1391548
terminate called without an active exception
[1]    21354 IOT instruction (core dumped)  obs

This happens while recording, streaming, or even while just having OBS open.

Steps to Reproduce
  1. Launch OBS
  2. Wait
  3. OBS will crash at some point in the next 5m-3h (approximately)
Anything else we should know?

KDE Wayland 6.3.3, NVIDIA 570.133.07 (opensource driver)

I've also tried running it with __NV_DISABLE_EXPLICIT_SYNC=1 set but it doesn't solve the problem.

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 with the linked OBS log and the reported X_GetProperty BadWindow output, then reproduce on Arch Linux with KDE Wayland and the listed NVIDIA driver while OBS is idle, recording, or streaming. Done means identifying the failing component and preventing the intermittent crash under the reported conditions, with a regression test or reproducible verification where applicable.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.