OBS High CPU Usage and General Issues

[CrossHyparu]

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

31.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/HzniOGY1nbRjJgl1

OBS Studio Crash Log URL

https://obsproject.com/logs/3TTOXRV0t17nUNX3

Expected Behavior

I expected OBS to perform as it has done previously. CPU usage was anywhere from 4-6% when running. It now sits at almost 3% idle.

Current Behavior

High CPU usage at idle, running at 12-15% when under load. previously OBS would idle at <1% and under load would be around 4%. I have made no changes to any OBS settings. I believe this is related to the new windows update which OBS is having conflicts with.

Several times during the stream, the Twitch chat and activity feed would go blank for several seconds and reload, sort of like they were crashing for a few seconds. At one point, it caused OBS to crash. I am unable to decipher the crash log so I am not sure what happened specifically.

Steps to Reproduce

1. Run a stream
2. Observe high CPU usage and chat/activity feed blanking out for several seconds.

...

Anything else we should know?

This was not an issue until this week. Over the weekend my PC forced updated Windows to 24H2. I believe this is directly a result of the update, and OBS is having compatibility issues that require addressing.

[mihawk90]

• likely possibly duplicate of Abnormally high CPU usage for OBS 31.0.0-betaX versions caused by obs-browser #11485

[RytoEX]

The linked crash log has to do with some issue in the code for handling Video Capture Devices on Windows.

Thread 15B8: (Crashed)
Stack            EIP              Arg0             Arg1             Arg2             Arg3             Address
00000096C5CFF0B8 00007FFFC2EC1152 CCCCCCCCCCCCCCCC 0000000000000000 0000000000000000 0000000000000107 obs.dll!os_breakpoint+0x2
00000096C5CFF0C0 00007FFFC2E94CEA CCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCC 000001AB3C5A25C0 CCCCCCCCCCCCCCCC obs.dll!video_frame_init+0x4aa
00000096C5CFF1F0 00007FFFC2E506FC 0000000000000000 0000000000000000 0000000000000000 00000096C5CFF390 obs.dll!obs_source_frame_init+0x5c
00000096C5CFF2B0 00007FFFC2E4ECAA 000001AB14C3F830 00000096C5CFF460 0000000000384000 CCCCCCCCCCCCCCCC obs.dll!obs_source_frame_create+0x5a
00000096C5CFF2E0 00007FFFC2E58B81 000001AB00000008 00000096C5CFF460 000001AB14C3F7F0 000001AB14C3F7F1 obs.dll!cache_video+0x291
00000096C5CFF360 00007FFFC2E5909D CCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCC 0000000000384000 CCCCCCCCCCCCCCCC obs.dll!obs_source_output_video2+0x1cd

At a glance, I'd suspect the bmalloc() call here to have size set to 0 somehow, triggering one of the os_breakpoint() calls in bmalloc():

obs-studio/libobs/media-io/video-frame.c

Line 223 in 0b2c858

frame->data[0] = bmalloc(size);

obs-studio/libobs/util/bmem.c

Line 104 in 0b2c858

os_breakpoint();

However, this likely has nothing to do with the observed behavior of the browser sources.

Several times during the stream, the Twitch chat and activity feed would go blank for several seconds and reload, sort of like they were crashing for a few seconds.

This sounds like CEF in the browser sources themselves are crashing. Chromium logs may be helpful, but that would require rebuilding obs-browser. A comment on #11485 says:

it looks related to hidden browser sources (activated on another screen, or marked hidden on the current scene).

Perhaps you could check for those.

[CrossHyparu]

Yes, this has been resolved. I was able to get confirmation in your Discord that it was the video capture source. I adjusted it and the problem was resolved. I really appreciate you getting back to me about this!

…

On Tue, Jan 21, 2025, 14:08 Ryan Foster ***@***.***> wrote: The linked crash log has to do with some issue in the code for handling Video Capture Devices on Windows. Thread 15B8: (Crashed) Stack EIP Arg0 Arg1 Arg2 Arg3 Address 00000096C5CFF0B8 00007FFFC2EC1152 CCCCCCCCCCCCCCCC 0000000000000000 0000000000000000 0000000000000107 obs.dll!os_breakpoint+0x2 00000096C5CFF0C0 00007FFFC2E94CEA CCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCC 000001AB3C5A25C0 CCCCCCCCCCCCCCCC obs.dll!video_frame_init+0x4aa 00000096C5CFF1F0 00007FFFC2E506FC 0000000000000000 0000000000000000 0000000000000000 00000096C5CFF390 obs.dll!obs_source_frame_init+0x5c 00000096C5CFF2B0 00007FFFC2E4ECAA 000001AB14C3F830 00000096C5CFF460 0000000000384000 CCCCCCCCCCCCCCCC obs.dll!obs_source_frame_create+0x5a 00000096C5CFF2E0 00007FFFC2E58B81 000001AB00000008 00000096C5CFF460 000001AB14C3F7F0 000001AB14C3F7F1 obs.dll!cache_video+0x291 00000096C5CFF360 00007FFFC2E5909D CCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCC 0000000000384000 CCCCCCCCCCCCCCCC obs.dll!obs_source_output_video2+0x1cd At a glance, I'd suspect the bmalloc() call here to have size set to 0 somehow, triggering one of the os_breakpoint() calls in bmalloc(): https://github.com/obsproject/obs-studio/blob/0b2c85845e20f41c612cfe2583e380bd436b6b3c/libobs/media-io/video-frame.c#L223 https://github.com/obsproject/obs-studio/blob/0b2c85845e20f41c612cfe2583e380bd436b6b3c/libobs/util/bmem.c#L104 However, this likely has nothing to do with the observed behavior of the browser sources. Several times during the stream, the Twitch chat and activity feed would go blank for several seconds and reload, sort of like they were crashing for a few seconds. This sounds like CEF in the browser sources themselves are crashing. Chromium logs may be helpful, but that would require rebuilding obs-browser. A comment on #11485 <#11485> says: it looks related to hidden browser sources (activated on another screen, or marked hidden on the current scene). Perhaps you could check for those. — Reply to this email directly, view it on GitHub <#11729 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXCC7ZKS3SV3GS5DBRVQD7D2L2LLRAVCNFSM6AAAAABVIXU5MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBVGUZTCMZQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TTVDINGUSS]

I am having this same issue I believe not really sure what is causing it. It has been happening since 2/2/2025.

Attached is my crash log
Crash 2025-02-12 23-40-39.txt

It will crash about every hour. I see that they have mentioned that it could have something to do with my camera but not sure how to keep this from happening.

I checked all drivers and everything is up to date and all windows updates are done as well.