macharborguy
Member
Was doing a broadcast today and noticed about 45 minutes into it that my 16GB of memory was completely used up, and that OBS was using around 14.5 GB of it.
Did a number of tests to see what the issue could have been and found part of the problem being the "console.log()" commands in many of my CLR Browser Sources. I used the console logs for testing, but didnt realize they would be causing problems in OBS overall.
Before I remove the console.log() functions I ran a test and OBS was chewing up about 20 Megs every second. After removing every single one I could, I got it down to chewing up just about 1 megabyte a second. After a test broadcast of 1h17m, OBS had used up close to 6 Gigs of physical memory according to the Task Manager.
Using the most recently available version of OBS, 64bit for Windows 7. 0.625 beta
here is a copy of my log file AFTER removing all of the console.log() stuff from my CLR Sources. NOTE: the very bottom of the log does say that memory leaks were detected... if anyone has some suggestions or additional questions, please post...
NOTE 2: I am broadcasting to an NGINX server that rebroadcasts to Hitbox and Twitch. I use the lower delay of Hitbox to do an instant replay for our eSports broadcasts of Guns of Icarus Online. I am adding an additional 4-6 second delay from within OBS to give some more headroom for the replays (if I could do this on the NGINX server, or just server side, that would be nice, especially if the delay is the issue).
NOTE 3: ending the broadcast/recording does NOT force OBS to release the memory. Only quitting OBS will free it back up.
======================================
log file attached to post
Did a number of tests to see what the issue could have been and found part of the problem being the "console.log()" commands in many of my CLR Browser Sources. I used the console logs for testing, but didnt realize they would be causing problems in OBS overall.
Before I remove the console.log() functions I ran a test and OBS was chewing up about 20 Megs every second. After removing every single one I could, I got it down to chewing up just about 1 megabyte a second. After a test broadcast of 1h17m, OBS had used up close to 6 Gigs of physical memory according to the Task Manager.
Using the most recently available version of OBS, 64bit for Windows 7. 0.625 beta
here is a copy of my log file AFTER removing all of the console.log() stuff from my CLR Sources. NOTE: the very bottom of the log does say that memory leaks were detected... if anyone has some suggestions or additional questions, please post...
NOTE 2: I am broadcasting to an NGINX server that rebroadcasts to Hitbox and Twitch. I use the lower delay of Hitbox to do an instant replay for our eSports broadcasts of Guns of Icarus Online. I am adding an additional 4-6 second delay from within OBS to give some more headroom for the replays (if I could do this on the NGINX server, or just server side, that would be nice, especially if the delay is the issue).
NOTE 3: ending the broadcast/recording does NOT force OBS to release the memory. Only quitting OBS will free it back up.
======================================
log file attached to post
