obsproject / obsproject/obs-studio

Hang when renaming scene collection (no reproducer but stack trace present)

Open
#13,495 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 11

Other OS

No response

OBS Studio Version

32.1.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/LMpBKwuLnvmmUIph

OBS Studio Crash Log URL

No response

Expected Behavior

It completes.

Current Behavior

It hangs.

Steps to Reproduce
  1. Under menu Scene Collection, click Rename.
  2. Type a new name and press Enter.
Anything else we should know?
Image

I attached Visual Studio and checked the stack trace. The program hung in on_actionRenameSceneCollection_triggered > SetupRenameSceneCollection > ActivateSceneCollection > Load > LoadData > ClearSceneData > obs_wait_for_destroy_queue. I did not check the stack trace of other threads before restarting the program.

I continued in Visual Studio and unplugged my active PCIe capture card's HDMI input cable, but OBS did not revive. Clicking the X button resulted in a log without the rename action visible.

I was experimenting with scenes, profiles, and scene collections in this session. I cannot reproduce this hang on further testing.

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 attached OBS log and trace the rename path from on_actionRenameSceneCollection_triggered through SetupRenameSceneCollection, ActivateSceneCollection, Load, LoadData, and ClearSceneData to obs_wait_for_destroy_queue. Investigate the reported hang and confirm that renaming a scene collection completes without blocking; the report does not provide a reliable reproducer or named test.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.