Resolve 14 Studio Crashes during Output

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

rickyrubb

  • Posts: 49
  • Joined: Mon Jul 29, 2013 11:17 pm

Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 5:05 am

Help...

I am working on a project in which I am pulling a key from a green screen. I have talent next to a monitor. The talent has skin tones that need to be pushed to the blues as per the client. It has a monitor in the shot that needs to be isolated and the gain brought down and the talents dress needs to be boosted from a black to a dark blue which is it's true color.

My set up is : One output node with a source image, Three Parallel nodes ( monitor, Skin tones and blue dress) a Parallel Mixer, a Key Mixer and an alpha output. All three Parallel Nodes are connected to both the Parallel Mixer and the Key Mixer.

The Monitor Node has a mask drawn around the monitor cutting all else out.
The Skin Tone Node has the "Face Refinement" effect applied with the "Use Mask" box checked. The talent is masked out (including the dress) cutting out all else.
The Blue Dress Node has an HSL key applied isolating the blue dress cutting out all else.

My problem is, when I render the thirty second clip the program crashes. I have rendered each individual node successfully and combinations successfully (minus the "Face Refinement" effect). The problem seems to be the "Face Refinement" effect.

The crashes seem to happen late like 70% when all nodes are active and 90% when the effect is used with fewer nodes. The crash however is not always the same. It does seem to be the same with a particular configuration. Like if I run it and it crashes and I run the same thing again it will crash at the same time.

Any thoughts or help would be greatly appreciated. This is a time sensitive piece and there are dozen more clips. I was hoping to do the work in resolve but I may have to resort back to my old standby After Effects.

Again Thanks
Offline
User avatar

Uli Plank

  • Posts: 21623
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

Re: Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 5:37 am

Did you update to 14.0.1?
For me it fixed the issues with face refinement.
Now that the cat #19 is out of the bag, test it as much as you can and use the subforum.

Studio 18.6.6, MacOS 13.6.6, 2017 iMac, 32 GB, Radeon Pro 580
MacBook M1 Pro, 16 GPU cores, 32 GB RAM and iPhone 15 Pro
Speed Editor, UltraStudio Monitor 3G
Offline

rickyrubb

  • Posts: 49
  • Joined: Mon Jul 29, 2013 11:17 pm

Re: Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 6:36 am

Just downloaded 14.0.1 uninstalled 14 installed 14.0.1. Tried a render it crashed at 71%.

I also have a 2 month old 27" IMac it has an eight GB graphics card + 24 GB of ram. I looked at the Activity Monitor an it doesn't go above 2GB.

R
Offline

Peter Chamberlain

Blackmagic Design

  • Posts: 13935
  • Joined: Wed Aug 22, 2012 7:08 am

Re: Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 6:41 am

DaVinci Resolve Product Manager
Offline

rickyrubb

  • Posts: 49
  • Joined: Mon Jul 29, 2013 11:17 pm

Re: Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 7:48 am

Sierra 10.12.6
iMac (Retina 5k, 27-inch 2017)
4.2 GHz Intel Core i7
24 GB 2400 MHz DDR4
Radeon Pro 580 8192 MB

Model Name: iMac
Model Identifier: iMac18,3
Processor Name: Intel Core i7
Processor Speed: 4.2 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 24 GB
2.11 Fusion Drive

The project sits on a 16TB USB3 Raid I'm not sure of the number but it is both speed and redundancy.

unfortunately the version of studio I have is an App Store Download (I am about to return it and purchase a dongle version).


Some required information is missing for email crash report, the crash archive will not be updated


==========[CRASH DUMP]========
Please send this to support:
#TIME Thu Oct 12 21:57:32 2017 - Uptime 00:07:28 (hh:mm:ss)
#FROM_EMAIL
#TO_EMAIL
#VERSION 14.0.1 (#008)
#SMTP_SERVER
#PROGRAM_NAME (64-bit)

0 Resolve 0x00000001031ac338 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 246712
1 libsystem_platform.dylib 0x00007fffc2db6b3a _sigtramp + 26
2 ??? 0x00000000000005a0 0x0 + 1440
3 libsystem_c.dylib 0x00007fffc2c3b420 abort + 129
4 libGPUSupportMercury.dylib 0x00007fffbb0edfbf gpumCreateComputeContext + 0
5 AMDRadeonX4000GLDriver 0x000000012243543a gldCreateDevice + 926
6 libGPUSupportMercury.dylib 0x00007fffbb0ee983 gpusQueueSubmitDataBuffers + 168
7 AMDRadeonX4000GLDriver 0x0000000122460d90 gldClearFramebufferData + 6096
8 AMDRadeonX4000GLDriver 0x0000000122460c76 gldClearFramebufferData + 5814
9 AMDRadeonX4000GLDriver 0x000000012246106d gldFinishQueue + 41
10 OpenCL 0x00007fffb17eab37 OpenCL + 6967
11 OpenCL 0x00007fffb17eb889 OpenCL + 10377
12 OpenCL 0x00007fffb1808db1 clSetEventCallback + 6771
13 OpenCL 0x00007fffb180c2a7 clFinish + 748
14 libdispatch.dylib 0x00007fffc2b718fc _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fffc2b72536 _dispatch_barrier_sync_f_invoke + 83
16 OpenCL 0x00007fffb180c11d clFinish + 354
17 OpenCL 0x00007fffb1807fb2 clSetEventCallback + 3188
18 OpenCL 0x00007fffb17fdcbc clEnqueueWriteBuffer + 814
19 Resolve 0x00000001034eb26c _ZN5boost16re_detail_10620012perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE16find_restart_litEv + 14300
20 Resolve 0x0000000104294ecc _ZNK4DVIP11DeviceImageIL7APIType1ENS_15GPUResourceTypeILS1_1EEEE8GetQueueEv + 732
21 Resolve 0x000000010388d1f2 _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 42834
22 Resolve 0x000000010388c01f _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 38271
23 Resolve 0x000000010388d372 _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 43218
24 Resolve 0x0000000103880fdc _ZN7VUMeterIdE9flushDataEv + 86412
25 Resolve 0x00000001034a0da3 _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 27491
26 Resolve 0x00000001034ad4de _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 78494
27 Resolve 0x00000001034ab529 _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 70377
28 libsystem_pthread.dylib 0x00007fffc2dc093b _pthread_body + 180
29 libsystem_pthread.dylib 0x00007fffc2dc0887 _pthread_body + 0
30 libsystem_pthread.dylib 0x00007fffc2dc008d thread_start + 13
Signal Number = 6
==============================
QObject::killTimer: Timers cannot be stopped from another thread
QObject::~QObject: Timers cannot be stopped from another thread
Resolve(1213,0x70000bb67000) malloc: *** error for object 0x608000a5a8b0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug


Some required information is missing for email crash report, the crash archive will not be updated


==========[CRASH DUMP]========
Please send this to support:
#TIME Thu Oct 12 21:57:32 2017 - Uptime 00:07:28 (hh:mm:ss)
#FROM_EMAIL
#TO_EMAIL
#VERSION 14.0.1 (#008)
#SMTP_SERVER
#PROGRAM_NAME (64-bit)

0 Resolve 0x00000001031ac338 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 246712
1 libsystem_platform.dylib 0x00007fffc2db6b3a _sigtramp + 26
2 ??? 0x000000011eb2fe00 0x0 + 4810014208
3 libsystem_c.dylib 0x00007fffc2c3b420 abort + 129
4 libsystem_malloc.dylib 0x00007fffc2d2afe7 szone_size + 0
5 libFairlightPage.dylib 0x0000000198c9e2e9 GetDLLUIInterface + 2893177
6 libFairlightPage.dylib 0x0000000198c9a688 GetDLLUIInterface + 2877720
7 libFairlightPage.dylib 0x0000000198c80401 GetDLLUIInterface + 2770577
8 libFairlightPage.dylib 0x0000000198ceed4b GetDLLUIInterface + 3223515
9 libFairlightPage.dylib 0x0000000198d02437 GetDLLUIInterface + 3303111
10 libFairlightPage.dylib 0x0000000198b81ef0 GetDLLUIInterface + 1728896
11 libFairlightPage.dylib 0x0000000198d0d129 GetDLLUIInterface + 3347385
12 libFairlightPage.dylib 0x0000000198d0130d GetDLLUIInterface + 3298717
13 libFairlightPage.dylib 0x0000000198b81ef0 GetDLLUIInterface + 1728896
14 libFairlightPage.dylib 0x00000001989ade84 GetDLLInterface + 4420
15 libFairlightPage.dylib 0x0000000198cf14ec GetDLLUIInterface + 3233660
16 libFairlightPage.dylib 0x0000000198cf1117 GetDLLUIInterface + 3232679
17 libFairlightPage.dylib 0x0000000198cf17f5 GetDLLUIInterface + 3234437
18 libFairlightPage.dylib 0x0000000198ca7ebe GetDLLUIInterface + 2933070
19 libsystem_c.dylib 0x00007fffc2c3c178 __cxa_finalize_ranges + 332
20 libsystem_c.dylib 0x00007fffc2c3c4b2 exit + 55
21 Resolve 0x00000001031ac73e _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 247742
22 libsystem_platform.dylib 0x00007fffc2db6b3a _sigtramp + 26
23 ??? 0x00000000000005a0 0x0 + 1440
24 libsystem_c.dylib 0x00007fffc2c3b420 abort + 129
25 libGPUSupportMercury.dylib 0x00007fffbb0edfbf gpumCreateComputeContext + 0
26 AMDRadeonX4000GLDriver 0x000000012243543a gldCreateDevice + 926
27 libGPUSupportMercury.dylib 0x00007fffbb0ee983 gpusQueueSubmitDataBuffers + 168
28 AMDRadeonX4000GLDriver 0x0000000122460d90 gldClearFramebufferData + 6096
29 AMDRadeonX4000GLDriver 0x0000000122460c76 gldClearFramebufferData + 5814
30 AMDRadeonX4000GLDriver 0x000000012246106d gldFinishQueue + 41
31 OpenCL 0x00007fffb17eab37 OpenCL + 6967
32 OpenCL 0x00007fffb17eb889 OpenCL + 10377
33 OpenCL 0x00007fffb1808db1 clSetEventCallback + 6771
34 OpenCL 0x00007fffb180c2a7 clFinish + 748
35 libdispatch.dylib 0x00007fffc2b718fc _dispatch_client_callout + 8
36 libdispatch.dylib 0x00007fffc2b72536 _dispatch_barrier_sync_f_invoke + 83
37 OpenCL 0x00007fffb180c11d clFinish + 354
38 OpenCL 0x00007fffb1807fb2 clSetEventCallback + 3188
39 OpenCL 0x00007fffb17fdcbc clEnqueueWriteBuffer + 814
40 Resolve 0x00000001034eb26c _ZN5boost16re_detail_10620012perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS6_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE16find_restart_litEv + 14300
41 Resolve 0x0000000104294ecc _ZNK4DVIP11DeviceImageIL7APIType1ENS_15GPUResourceTypeILS1_1EEEE8GetQueueEv + 732
42 Resolve 0x000000010388d1f2 _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 42834
43 Resolve 0x000000010388c01f _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 38271
44 Resolve 0x000000010388d372 _ZN10ReactorGPU29TemporalSupportFramesAccessorItE20GetSupportFramesRGBAENS_23SupportFramesAccessModeEii + 43218
45 Resolve 0x0000000103880fdc _ZN7VUMeterIdE9flushDataEv + 86412
46 Resolve 0x00000001034a0da3 _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 27491
47 Resolve 0x00000001034ad4de _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 78494
48 Resolve 0x00000001034ab529 _ZN10ReactorGPU14PitchConverterIL7APIType1EE7ConvertERNS_12MemoryBufferERKS3_NS_14MemoryDataTypeES7_mmPNS_18MemoryCacheManagerE + 70377
49 libsystem_pthread.dylib 0x00007fffc2dc093b _pthread_body + 180
Signal Number = 6
==============================
libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >: boost: mutex lock failed in pthread_mutex_lock: Invalid argument


Some required information is missing for email crash report, the crash archive will not be updated


==========[CRASH DUMP]========
Please send this to support:
#TIME Thu Oct 12 21:57:32 2017 - Uptime 00:07:28 (hh:mm:ss)
#FROM_EMAIL
#TO_EMAIL
#VERSION 14.0.1 (#008)
#SMTP_SERVER
#PROGRAM_NAME (64-bit)

0 Resolve 0x00000001031ac338 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 246712
1 libsystem_platform.dylib 0x00007fffc2db6b3a _sigtramp + 26
2 ??? 0x000000040c72b358 0x0 + 17388712792
3 libsystem_c.dylib 0x00007fffc2c3b420 abort + 129
4 libc++abi.dylib 0x00007fffc178e94a __cxa_bad_cast + 0
5 libc++abi.dylib 0x00007fffc17b3c17 _ZL25default_terminate_handlerv + 243
6 libobjc.A.dylib 0x00007fffc22c3713 _ZL15_objc_terminatev + 124
7 libc++abi.dylib 0x00007fffc17b0d49 _ZSt11__terminatePFvvE + 8
8 libc++abi.dylib 0x00007fffc17b0dc3 _ZSt9terminatev + 51
9 libFairlightPage.dylib 0x0000000198b9d65f GetDLLUIInterface + 1841391
10 libFairlightPage.dylib 0x0000000198fe92fa kiss_fftri + 2354090
11 libFairlightPage.dylib 0x0000000199099699 _ZN5boost6thread21start_thread_noexceptEv + 409
12 libsystem_pthread.dylib 0x00007fffc2dc093b _pthread_body + 180
13 libsystem_pthread.dylib 0x00007fffc2dc0887 _pthread_body + 0
14 libsystem_pthread.dylib 0x00007fffc2dc008d thread_start + 13
Signal Number = 6
==============================
QObject::~QObject: Timers cannot be stopped from another thread


I don't know if this helps or hurts. Maybe it's to much or not enough or the wrong stuff.

If so sorry

r
Offline

Peter Chamberlain

Blackmagic Design

  • Posts: 13935
  • Joined: Wed Aug 22, 2012 7:08 am

Re: Resolve 14 Studio Crashes during Output

PostFri Oct 13, 2017 11:27 am

Can you post a link to the log Resolve generates from the help menu?
DaVinci Resolve Product Manager
Offline

rickyrubb

  • Posts: 49
  • Joined: Mon Jul 29, 2013 11:17 pm

Re: Resolve 14 Studio Crashes during Output

Offline

rickyrubb

  • Posts: 49
  • Joined: Mon Jul 29, 2013 11:17 pm

Re: Resolve 14 Studio Crashes during Output

PostSat Oct 14, 2017 6:48 am

Ok, I worked around the problem.

I used "Face Refinement" on the original footage with the green background. I used "use mask" and pushed the skin tones into the blues. Then rendered that out. Imported the clips and pulled the key, Isolated the monitor and blue dress and rendered the composite.

The "Face Refinement" render crashed each time. I rendered 17 clips all approximately 30 seconds each. I don't have all the crash points. I didn't start writing them down at the beginning but I have them from the last one backwards. The process was Render- Crash- Re Render- Complete and repeat... 17 times. Twice the render completed on the first pass. The second Round of rendering, the one where I pulled the key went great. Quick and painless.

Crash times
52% 82%
47%. 77%
37%. 69%
39%. Completed
54%. 9% Froze the computer (Force Quit)
36%. Completed
72%

Any way the footage looks good and I will use the "Face Refinement" tool sparingly. Maybe the clips were too long.

Return to DaVinci Resolve

Who is online

Users browsing this forum: AviatorDed, Johannes Hoffmann, panos_mts, Vangelis and 157 guests