obsproject
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
- Open OBS
- Plug in an HDMI capture card
- 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
- Don't notice for a day or two
- 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.
This is a format error being thrown from the capture card itself, you would need to switch to a format the card supports or use a different capture card that supports this format. That being said, I agree that a log size limit would be a good idea but I wanted to post this reply to at least make you aware of what is causing it in this case.
@prgmitchell the issue is not with the error, the issue is with the log system that allows ANY capture card to create a 14gb log file, regardless of how poorly behaved
On Sun, Oct 1, 2023, 1:12 PM prgmitchell @.***> wrote:
This is a format error being thrown from the capture card itself, you would need to switch to a format the card supports or use a different capture card that supports this format.
— Reply to this email directly, view it on GitHub https://github.com/obsproject/obs-studio/issues/9652#issuecomment-1742157181, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABZCV5DY4PJXXNLQU6U5ZTX5GW7RANCNFSM6AAAAAA5OPTUK4 . You are receiving this because you authored the thread.Message ID: @.***>
I don't think anyone disagrees, but it's important context that this is a very, very rare occurrence, and the issue is actually related to the error message itself.
We already have protections against this with duplicate log line detection, but it's only checking single lines, not 3 repeated. This is a very unique and specific edge case where the protections we DO have are not kicking in. Since this doesn't really ever come up in normal operation (typically someone will not be trying to access a capture device that isn't properly configured or connected to anything, and in such cases, almost all capture devices default to some "no signal" output anyway), it hasn't been something we've felt worth looking in to further.
There's likely a solution here somewhere, though. Hopefully the extra context helps.
Fair enough. To explain a little bit more about my setup, I play Switch regularly and have it connected to my capture card as part of my normal setup, and the audio routes through my capture card and through OBS so that I can listen to my music at the same time. I keep OBS running in the background on my computer most of the time in case I want to quickly take a screenshot or record something. Occasionally there seems to be some kind of handshake error with the capture card and I need to deactivate and reactivate the source in OBS, but that's a very rare occurrence (maybe once a month or less)
On Sun, Oct 1, 2023, 2:45 PM Joel Bethke @.***> wrote:
I don't think anyone disagrees, but it's important context that this is a very, very rare occurrence, and the issue is actually related to the error message itself.
We already have protections against this with duplicate log line detection, but it's only checking single lines, not 3 repeated. This is a very unique and specific edge case where the protections we DO have are not kicking in. Since this doesn't really ever come up in normal operation (typically someone will not be trying to access a capture device that isn't properly configured or connected to anything, and in such cases, almost all capture devices default to some "no signal" output anyway), it hasn't been something we've felt worth looking in to further.
There's likely a solution here somewhere, though. Hopefully the extra context helps.
— Reply to this email directly, view it on GitHub https://github.com/obsproject/obs-studio/issues/9652#issuecomment-1742181058, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABZCV4OFK7NKQEAGCSNE7DX5HB3ZANCNFSM6AAAAAA5OPTUK4 . You are receiving this because you authored the thread.Message ID: @.***>
Happened again, first warning i got is that the game I was playing crashed and discord crashed and then when it started it was stuck in a "can't install updates" bootloop—i spent like half an hour trying and failing to download the installer from the website (with that also mysteriously failing) before I thought to check the free disk space
Is the error message the same? If it is the same, I don't think we need further confirmation of the same issue.
Has this definitely been isolated to the capture card? If so, what capture card is this?
