OBS crashes after using Replay Buffer for a small amount of time

[Zukimentsu]

Operating System Info

macOS 15

Other OS

No response

OBS Studio Version

31.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/NC4M2PzPXGEmgVBx

OBS Studio Crash Log URL

Crash Report OBS 31.0.0.txt

Expected Behavior

I expected Replay Buffer not to cause a crash

Current Behavior

When replay buffer is on and when it gets around the 8 Gig memory mark, or after around 10-15 minutes, it crashes.

Steps to Reproduce

1. Start Replay Buffer
2. Wait 10-15 minutes
3. Crash happens
   ...

Anything else we should know?

I used ProRes Proxy as my Hardware Encoder for Recording. I even switched to the Apple HEVC Hardware Encoder afterwards to see if ProRes is an issue but the crash still happens.

macOS crash report

Process: OBS [2554]
Path: /Applications/OBS.app/Contents/MacOS/OBS
Identifier: com.obsproject.obs-studio
Version: 31.0.0 (12207818817)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 502

Date/Time: 2024-12-11 02:19:13.7624 -0500
OS Version: macOS 15.1.1 (24B2091)
Report Version: 12
Anonymous UUID: 6830E81E-A94A-22D2-C71D-77EB68CCCC9C

Sleep/Wake UUID: A1B20E84-4CF2-4410-82F1-80DC9896E8A4

Time Awake Since Boot: 15000 seconds
Time Since Wake: 1340 seconds

System Integrity Protection: enabled

Crashed Thread: 5 video-io: video thread

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000303fb79b8

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Termina

FULL macOS Crash Report
Crash Report OBS 31.0.0.txt
ting Process: exc handler [2554]

[jcm93]

What was your replay buffer duration (or memory limit) set to when you're seeing this crash?

[Zukimentsu]

What was your replay buffer duration (or memory limit) set to when you're seeing this crash?

I have my video output set to advanced but I am unable to set a memory usage limit. I could’ve sworn I was able to do that before

[jcm93]

Memory usage limit is only available for encoder rate control types that are not directly bitrate-based (i.e. CRF/CQP, not ABR/VBR/CBR). It is also not available with ProRes, but due to a bug.

Without a memory limit you should still be setting the replay buffer duration; what do you have set there?

[Zukimentsu]

Memory usage limit is only available for encoder rate control types that are not directly bitrate-based (i.e. CRF/CQP, not ABR/VBR/CBR). It is also not available with ProRes, but due to a bug.

Without a memory limit you should still be setting the replay buffer duration; what do you have set there?

It used to be 3 minutes but now it is 1 minute and 30 seconds

[jcm93]

So far I have been unable to reproduce this locally.

Are you able to check if the issue occurs in a new minimal scene collection, with e.g. only one source such as a macOS screen capture, or capture card device source?

[Zukimentsu]

So far I have been unable to reproduce this locally.

Are you able to check if the issue occurs in a new minimal scene collection, with e.g. only one source such as a macOS screen capture, or capture card device source?

Right now, I am unable to reproduce the issue because I already downgraded to the previous version of OBS and I have no problems now

[JRemitz]

This is an interesting observation. v31 has been very unstable for me as well but I couldn't pin it on the replay buffer. My streams are usually right around 1 hour to 1 hour and 20 minutes. They would crash at least twice per stream. I have a 10s replay buffer, running version 31. Yesterday I made sure to stop and start the replay buffer roughly every fifteen to twenty minutes and the stream stayed alive the entire time. I'm happy to share other information if it's useful. I do not have a handy crash report, unfortunately.

EDIT: and I only use one plugin, which is the dir-watch-media plugin and I'm running the latest version

[jcm93]

You should check Console.app for Crash Reports via the left sidebar, and attach any from OBS; without a report it is difficult to know if you are looking at the same issue.

[JRemitz]

Okay interesting. Scanning through crash report history, the VCPHandGestureVideoRequestSerialQueue is the thread that is crashing regularly. Not sure if related here or if I should open up as a new issue?

[JRemitz]

I'll open a new issue later with crash reports and link here in reference to restarting the replay buffer as a possible mitigation tactic. Thank you!

[jcm93]

I'll open a new issue later with crash reports and link here in reference to restarting the replay buffer as a possible mitigation tactic. Thank you!

Do you have this crash report?

[jcm93]

After investigating this more, it looks like there is currently a bug where OBS 31.0 will crash on macOS if it uses more than 8 GB of memory.

More specifically, it seems to be an issue with the memory allocator and deallocator hijacking done by the updated CEF used in OBS 31.

[JRemitz]

Ah I'm sorry @jcm93 - I didn't submit but I still can. Would it be helpful? Here or a different issue?

[jcm93]

Feel free to attach it here; I think this issue thread can probably become a catch-all for crashes caused by >8GB memory use, and if it's something else it can just be marked off-topic.

[DowntownNB]

Experiencing the same issue on Windows 11. Crash log provided below. Is any more info needed?

Crash log: https://obsproject.com/logs/vxBMBgKYe1zrmuwL

[Fenrirthviti]

Experiencing the same issue on Windows 11. Crash log provided below. Is any more info needed?

Crash log: https://obsproject.com/logs/vxBMBgKYe1zrmuwL

Your crash is being caused by the replay-source plugin, and should be reported to the developer.