Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OBS Memory Usage Issue #368

Open
mdiamond1 opened this issue Aug 15, 2023 · 3 comments
Open

OBS Memory Usage Issue #368

mdiamond1 opened this issue Aug 15, 2023 · 3 comments

Comments

@mdiamond1
Copy link

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
OBS Memory

@mdiamond1
Copy link
Author

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!

@mohsindlb
Copy link

Thanks @mdiamond1 for reporting this issue! We are looking into it and will get back to you with further updates.

@mohsindlb
Copy link

Hello @mdiamond1 Can you please provide correct ‘dmp’ file for WinDbg for further investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants