You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
OBS crashing if launched after DaVinci Resolve has run
- Thread starter Binho
- Start date
Lawrence_SoCal
Active Member
Crash logs aren't an area of expertise for me, but while waiting for a more knowledgeable response here is my $0.02
Running both should fine *IF* you have adequate resources (RAM, CPU, Disk I/O, etc) .... But your circa late 2013 CPU is ancient for the VERY computationally demanding of real-time video encoding. So for you, yea, running both makes no sense. BTW, Which GPU are you using, and are you using a GPU encode offload in OBS?
Starting and running Resolve, and then exiting Resolve should be fine... assuming you don't have other OS issues (like a memory leak somewhere). or corrupted memory in QuickSync or other GPU?
Simple test
- boot OS and let sit for 5-15 minutes to hit a steady state
- Check RAM usage and free memory
- Use Resolve, then exit Resolve
- Check RAM usage and free memory again. If RAM usage much higher, that may indicate a problem
check OS Processes to make sure Resolve (or related plugins?) still not running. IF you have a HDD vs SSD, Resolve shutting down may take some time. Are you allowing Resolve enough time to fully close?
Assuming a small memory leak, that in and of itself shouldn't cause OBS to crash (I wouldn't think). Though a kludgey work-around, at least faster than a reboot - Have you tried just logging off (OS User Profile) and logging back in?
Running both should fine *IF* you have adequate resources (RAM, CPU, Disk I/O, etc) .... But your circa late 2013 CPU is ancient for the VERY computationally demanding of real-time video encoding. So for you, yea, running both makes no sense. BTW, Which GPU are you using, and are you using a GPU encode offload in OBS?
Starting and running Resolve, and then exiting Resolve should be fine... assuming you don't have other OS issues (like a memory leak somewhere). or corrupted memory in QuickSync or other GPU?
Simple test
- boot OS and let sit for 5-15 minutes to hit a steady state
- Check RAM usage and free memory
- Use Resolve, then exit Resolve
- Check RAM usage and free memory again. If RAM usage much higher, that may indicate a problem
check OS Processes to make sure Resolve (or related plugins?) still not running. IF you have a HDD vs SSD, Resolve shutting down may take some time. Are you allowing Resolve enough time to fully close?
Assuming a small memory leak, that in and of itself shouldn't cause OBS to crash (I wouldn't think). Though a kludgey work-around, at least faster than a reboot - Have you tried just logging off (OS User Profile) and logging back in?
Thank you for your support. I ran the test you suggested and some 30 seconds after closing Resolve the memory usage dropped back to about the same level it was before launching Resolve.Crash logs aren't an area of expertise for me, but while waiting for a more knowledgeable response here is my $0.02
Running both should fine *IF* you have adequate resources (RAM, CPU, Disk I/O, etc) .... But your circa late 2013 CPU is ancient for the VERY computationally demanding of real-time video encoding. So for you, yea, running both makes no sense. BTW, Which GPU are you using, and are you using a GPU encode offload in OBS?
Starting and running Resolve, and then exiting Resolve should be fine... assuming you don't have other OS issues (like a memory leak somewhere). or corrupted memory in QuickSync or other GPU?
Simple test
- boot OS and let sit for 5-15 minutes to hit a steady state
- Check RAM usage and free memory
- Use Resolve, then exit Resolve
- Check RAM usage and free memory again. If RAM usage much higher, that may indicate a problem
check OS Processes to make sure Resolve (or related plugins?) still not running. IF you have a HDD vs SSD, Resolve shutting down may take some time. Are you allowing Resolve enough time to fully close?
Assuming a small memory leak, that in and of itself shouldn't cause OBS to crash (I wouldn't think). Though a kludgey work-around, at least faster than a reboot - Have you tried just logging off (OS User Profile) and logging back in?
For some reason, today OBS is not crashing like last week, when it would crash immediately after launching, every time. It did crash once though, while I was changing the mode of a video source, but then relaunched with no problem.
My graphics card is a GeForce GTX 1080 and I am using the NVENC H.264 encoder and all the settings recommended by NVIDIA.
Update: OBS crashes every time I change any setting for my Decklink Mini Recorders while there is an active input in these devices. If the input is SDI, it won't crash if I swich the Video Connection to HDMI before changing the setting and vice-versa.
OBS never crashes when I change the settings for my Intensity Pro card, though.
OBS never crashes when I change the settings for my Intensity Pro card, though.
Attachments
Update: I started a new scene collection from scratch and OBS stopped crashing. I went back to the previous collection and it started crashing again. The main difference is that the previous collection contained nested scenes. When the PC can't handle nested scenes, OBS should give some kind of warning.