OTOY Forums

[OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment variable to enable.)
25832: Fatal error: Segmentation fault\

Hi all. I did some searching on the forum and found some other people had these problems. I can sometimes render 10 frames, sometimes 50, sometimes 1. I get the above error.
Houdini 18.5.351 Octane 2020.2.0.4 Windows

It was working fine last night (my previous version of Octane). I literally walked away, came back 5 mins later, tried another frame and I was getting nothing (black in Mplay, black in IPR) I updated OCtane to latest. It started rendering again, but now with the new crash.

This also appears in the console now when I start Houdini.
[OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment variable to enable.)

Do I need to disable OCIO in my Houdini .env?

I went to the OCIO site and downloaded an OCIO config just to give a path for Houdini to point to a file. The rendering is working so far but this popped up in the console

[OpenColorIO Info]: Color management disabled. (Specify the $OCIO environment variable to enable.)
*** OCTANE API MSG: Tried to access null item
*** OCTANE API MSG: Tried to access null item

**update** nope, crashed again Is this getting worked on or should I just revert to an older version for the time being. Cheers

hi,
I have the same problem too..

i use
windows 10
rtx 3090 tuv
amd treadtripper 2990wx
houdini 18.5

The console message comes from the Octane core and it is only information about the fact that it can't initialize OCIO, but it is not a critical issue at all, so the crash must come from another problem at the render time. Later this week we are going to release a new plugin build including the latest Octane 2020.2.1 core. If you still have this problem with this new build, let us know to further investigate it.

Thanks,
-Juanjo

The new Octane 2020.2.1.1 build is ready. Can you please check if the crash problem is still there in this new build?

Thanks,
-Juanjo

Hi;

I am also experiencing very similar behavior as described here; I can render a scene for only a handful of frames, then I get a "Segmentation Fault" message and houdini crashes.

I'm on Windows 10, and as of this writing, have the latest Octane and Nvidia Studio graphics drivers installed. I am rendering on a two-GPU system, using one 1080 and one 1080ti card.

What are some things I can do to help troubleshoot this? Are there log files or other resources I can provide or spelunk myself to be useful? I'm not sure where to start investigating...

Can you please enable the Octane log file in debug mode in the plugin options panel and attach the log file that you get after the crash? If you can send us the scene to reproduce the problem here, it could also help a lot.

Thanks,
-Juanjo

Hi! Took me a while but here's my crash log. Again, it happens when I'm rendering a sequence. Single frames are fine. Here's a dxdiag doc also. Some interesting info at the bottom about Houdini crashing. Might be of interest. Cheers!

theshizon wrote:Hi! Took me a while but here's my crash log. Again, it happens when I'm rendering a sequence. Single frames are fine. Here's a dxdiag doc also. Some interesting info at the bottom about Houdini crashing. Might be of interest. Cheers!

Sorry, are you rendering the scene in full scene reload mode? I'm investigating a crash that happens while cleaning the scene that seems related to your issue.

Thanks,
-Juanjo

I believe I was in this case. I know for sure I was when I had originally posted of the crashing previously. I needed to use Full scene reload because I was using changing point attributes to drive a shader.