Question / Help Massive 70+ GB "debug.log" file being generated while running OBS.

[MachineDynamics]

Has anyone else had issues with generating a single massive log file?

I nearly ran out of drive space during a recording session. I checked my local recordings, and they barely accounted for half the free space I had when I started, so I ran windirstat, and I find a massive log file that OBS is generating whenever it's running, and it seems to grow in size indefinitely. The offending log file is being created in the same directory as the OBS executable, rather than the normal log file directory.

Attached are a windirstat screenshot, and the most recent normal log file that OBS is supposed to be generating.

 

[ethaniel]

Yep. I confirm this problem as well. It needs to be addressed by developers.

 

[Harold]

Figure out why your browser sources are so chatty then

 

[ethaniel]

@Harold shouldn't be my problem. I'm very limited on space and would prefer all the log files purged.

 

[Suslik V]

@ethaniel Try to make new small file named "debug.log" under the same directory and in properties of the file check the "read-only" attribute.
And sure, you need to look at this big log-file to know why Browser Source is verbose for you.

 

[ethaniel]

Yeah, it's a good idea. But still, it's a workaround. Many people don't know about this problem - it would be cool if OBS took care of it.

 

[Raikyaku]

i just delete the file, 79GB... the obs still works for me.

 

[R1CH]

The debug.log contains output from pages you have opened in the browser source. If it grows to that kind of size you should examine what is being output as it is likely a repeated error from one of the pages.

Deleting it is of course fine, but it will continue to be written if you run OBS as admin and have a page open that is generating errors.

 

[Redolent Thought]

These log files generate 30-200gb space per *stream* I do... 1 hour; 4 hours... This is garbage.

 

[qhobbes]

Right click on the debug.log file, Properties, Security, Edit..., select the Admin user, check the box for Deny for Write, Apply, OK, OK.

 

[Redolent Thought]

Right click on the debug.log file, Properties, Security, Edit..., select the Admin user, check the box for Deny for Write, Apply, OK, OK.

Just saw this. Just clicked through it - gonna give it a shot. I've gotten used to deleting these 170GB files on the daily, but I hope this works. THANK YOU, if it does!!!