FFMPEG warnings flooding OBS log

Open
#10,134 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
audio-video-rtc

Research direction

Start with the OBS Studio log linked in the issue and reproduce the flood using an HLS URL through a Media Source, as described in the steps. Trace where the repeated FFMPEG warning reaches the logger; done means a failing stream cannot generate an unbounded log file while the underlying warning remains diagnosable.

Written by the indexing model from the issue text.

Description

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

Other

OBS Studio Version (Other)

30.0.0

OBS Studio Log URL

https://pastebin.com/VQu45BFg

OBS Studio Crash Log URL

No response

Expected Behavior

I would expect logger to ignore repeated lines in some way or another, generating 300GB log file is unacceptable.

Current Behavior

Log file gets flooded with FFMPEG errors, generated hundreds of times per 0.001s

Steps to Reproduce
  1. Add a HLS input via Media Source
  2. Have the input stream cause FFMPEG to produce warning: inflate return value: -3, incorrect header check error (I am unsure what exactly casues those kinds of errors)
  3. Log file gets flooded with approximately hundreds of warnings per 0.001s
Anything else we should know?

Media source Input was a M3U8 URL, Input Format was set to hls. I am not sure if this is correct way to do it but it resulted in working input.

I left OBS running in the background, at some point the stream probably errored out FFMPEG and the flood gates were opened.

Last 1000 lines of log uploaded to pastebin, since the original file got up to 286GBs.

I noticed what's happening just as my system was running out of storage, fortunately. If I didn't it could possibly cause some serious trouble.

image_2024-01-24_042028379

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

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.

More from obsproject/obs-studio

All issues in obsproject/obs-studio

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.