obsproject / obsproject/obs-studio

Memory leak when --disable-missing-files-check is used

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

Ubuntu 22.04

Other OS

No response

OBS Studio Version

30.2.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/BvNHbI5BxygZL2lw

OBS Studio Crash Log URL

No response

Expected Behavior

No memory leak should occur when using the --disable-missing-files-check flag.

Current Behavior

Use of --disable-missing-files-check (when there are any missing files) actually does allocate and build the list of missing files - the flag just inhibits the display of the dialog - but also accidentally inhibits the release of the files list ...

Number of memory leaks: 1
Steps to Reproduce
  1. Construct a scene with a file reference.
  2. Exit OBS.
  3. Remove the file.
  4. Start OBS with the --disable-missing-files-check flag.
  5. Exit OBS. Observe Number of memory leaks: 1 in the output log.
Anything else we should know?

No response

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 reproducing the leak with a missing scene file and the --disable-missing-files-check flag, then compare the missing-files handling with the normal exit path. Done means OBS exits without reporting a memory leak when the flag is used.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.