Excessive log file usage (14 Gb in a single file)

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

29.1.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

I assume OBS will be unhappy if I upload a 14 gb log file

OBS Studio Crash Log URL

No response

Expected Behavior

I expect the software to truncate, cycle or compress its log files at a certain length, to avoid using excessive disk space

Current Behavior

The log file is filled up with variants of the following:

19:05:17.245: Error decoding video
19:05:17.277: warning: Found EOI before any SOF, ignoring
19:05:17.277: fatal:   No JPEG data found in image
19:05:17.277: Error decoding video
19:05:17.309: warning: Found EOI before any SOF, ignoring
19:05:17.309: fatal:   No JPEG data found in image
19:05:17.309: Error decoding video
19:05:17.341: warning: Found EOI before any SOF, ignoring
19:05:17.341: fatal:   No JPEG data found in image
19:05:17.341: Error decoding video
19:05:17.389: warning: Found EOI before any SOF, ignoring
19:05:17.389: fatal:   No JPEG data found in image
19:05:17.389: Error decoding video
19:05:17.421: warning: Found EOI before any SOF, ignoring
19:05:17.421: fatal:   No JPEG data found in image
19:05:17.421: Error decoding video
19:05:17.453: warning: Found EOI before any SOF, ignoring
19:05:17.453: fatal:   No JPEG data found in image
19:05:17.453: Error decoding video
19:05:17.485: warning: Found EOI before any SOF, ignoring
19:05:17.485: fatal:   No JPEG data found in image
19:05:17.485: Error decoding video
19:05:17.517: warning: Found EOI before any SOF, ignoring
19:05:17.517: fatal:   No JPEG data found in image
19:05:17.517: Error decoding video
19:05:17.549: warning: Found EOI before any SOF, ignoring
19:05:17.549: fatal:   No JPEG data found in image
19:05:17.549: Error decoding video
19:05:17.581: warning: Found EOI before any SOF, ignoring
19:05:17.581: fatal:   No JPEG data found in image
19:05:17.581: Error decoding video
19:05:17.613: warning: Found EOI before any SOF, ignoring
19:05:17.613: fatal:   No JPEG data found in image
19:05:17.613: Error decoding video
19:05:17.645: warning: Found EOI before any SOF, ignoring
19:05:17.645: fatal:   No JPEG data found in image
19:05:17.645: Error decoding video
19:05:17.677: warning: Found EOI before any SOF, ignoring
19:05:17.677: fatal:   No JPEG data found in image
19:05:17.677: Error decoding video
19:05:17.709: warning: Found EOI before any SOF, ignoring
19:05:17.709: fatal:   No JPEG data found in image
19:05:17.709: Error decoding video

at a rate of about ~1GB per day of having the application open in the background (with on and off usage to record some of my switch games). After a few months, I have a 30GB directory of these.

Steps to Reproduce

1. Open OBS
2. Plug in an HDMI capture card
3. Don't turn on device the card is connected to? Have some sort of error? In some way, trigger the jpeg decoding error found in the log file
4. Don't notice for a day or two
5. Find a 2GB log file.

Anything else we should know?

Having to manually remember to clear out my log files every few months when Windows complains about low disk space on my boot drive SSD is pretty annoying, would love if there was some automated max log file size built in to OBS. A quick google search finds a lot of people complaining about this but no solutions.

No source file, test, or entry point is named in the report. Start by reproducing the repeated JPEG decoding errors with an HDMI capture card on Windows and trace where OBS writes its log files; done means repeated errors no longer allow an individual log or the log directory to consume excessive disk space.