You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to use OBS to stream an audio-only feed to the Dolby.io platform, an error is received each time after approx. 7/8 mins saying that OBS has crashed (attached log). When looking at the task manager, this appears to be a memory issue where OBS is taking up to around 90% of the memory available. When the same laptop is downgraded to Windows 10, the same issue exists and we are seeing the same issue on other laptops with Windows 11 installed.
When using the version prior to this (1.4.2-28.1.2-m104) the same issue occurs (crash logs attached).
When using version 26.1.2 m90-2.21 on the same machine (and Windows 10) no issue is experienced and the stream works perfectly with only 5% of memory usage reported.
The stream is for a high profile, mission critical event, so we will likely stick to the earlier version unless some other alternative can be seen as reliable.
One other update regarding version 26.1.2 m90-2.21 - just discovered that when stopping the stream, OBS crashes. This doesn't make it unusable for us, but it would be good if it didn't crash!
OBS: Release 1.5.0 (OBS-Studio 28.1.2 WebRTC m108)
OS: Windows 11
Device: Lenovo Legion 5 15ACH6H (AMD Ryzen 7, 8GB RAM, NVIDIA GeForce RTX 3060)
Streaming Platform: Dolby.io
When attempting to use OBS to stream an audio-only feed to the Dolby.io platform, an error is received each time after approx. 7/8 mins saying that OBS has crashed (attached log). When looking at the task manager, this appears to be a memory issue where OBS is taking up to around 90% of the memory available. When the same laptop is downgraded to Windows 10, the same issue exists and we are seeing the same issue on other laptops with Windows 11 installed.
When using the version prior to this (1.4.2-28.1.2-m104) the same issue occurs (crash logs attached).
When using version 26.1.2 m90-2.21 on the same machine (and Windows 10) no issue is experienced and the stream works perfectly with only 5% of memory usage reported.
The stream is for a high profile, mission critical event, so we will likely stick to the earlier version unless some other alternative can be seen as reliable.
Crash 2023-08-14 16-33-03.txt
Crash 2023-08-14 16-49-18.txt
The text was updated successfully, but these errors were encountered: