One of our SAs asked me the same question for you folks. I’m a bit stumped myself.
Usually if a program works outside of Deadline but not inside, it’s related to what the environment variables are set to. A 139 denotes a segmentation fault on Unix, which means the application tried to use memory it wasn’t allowed to. That’s most often caused by C/C++ pointers not being checked before accessing them.
Can you try testing your environment in both scenarios? Just run “/usr/bin/env” from your shell, and from the Command Line plugin then compare them to see how they’re different.
You can add or change a variable on your command line job for testing. You can also make those changes more permanent either at the OS level or using some deadline scripts.
Hi, I got the same problem here (with Renderman), could you please tell me some more detail information? The shell is from Deadline or somewhere else?
(I got error 139 but if I run a simple scene(some boxes with light) it works well through Deadline, but if I run a serious heavy scene it’s not working and keep report error 139)
Hi, sorry I cannot really remember how did I solve it, but could you try to check each elements in your scene one by one? I think something wrong with one asset or some attributes. maybe try to delete all unnecessary attributes and group.
hope this can help