CGRU not catching C4D errors:
Posted: Mon Sep 04, 2017 2:36 pm
There are a few errors that are thrown by C4D / Octane that CGRU does not currently detect, so it does not re-queue the failed tasks and requires careful human monitoring to catch and fix. Here is the only info that we get in the logs from these crashes:
1) most common:
1) most common:
2) less common:Error: application crashed
C4DUnhandledExceptionFilter: writing exception info
C4DUnhandledExceptionFilter: writing call stacks
<<< Render failure detected!!! >>> Please check render statistics to solve the problem. Device:0 TotMem:12Gb rtData:254Mb film:182Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.082Gb temperature:65 Device:1 TotMem:12Gb rtData:254Mb film:182Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.082Gb temperature:71 Device:2 TotMem:12Gb rtData:254Mb film:22Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.224Gb temperature:67 Check geometry subdivisons. Picture viewer uses 'Render' subdivisions. But Live Viewer uses 'Editor' subdivision values. Try to decrease 'render/editor' subdivison values. Failure... MotBlurTM=0 sec. createTM=5.683 sec. matTM=3.89 sec. updateTM=20.102 sec. Device:0 TotMem:12Gb rtData:254Mb film:182Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.082Gb temperature:65 Device:1 TotMem:12Gb rtData:254Mb film:182Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.082Gb temperature:71 Device:2 TotMem:12Gb rtData:254Mb film:22Mb geo:171Mb node:7Kb tex:279Mb unavailable:2.224Gb temperature:67 renderTM:0.671ms. totalTM:26.457ms.