Hi,

I get this Karma error after few frames.

Warning
Failed to complete render: exit code 139
Use a Log Viewer with External Render Processes enabled for more information.

How can I get to this Log Viewer the error talks about?

Thanks,

I have simplified the render settings to try to debug from what it comes.

Now I only have no Beauty Pass, an N and Albedo pass, and I get the error.
While that same object perfectly renders the whole sequence in a XPU Karma render,

I have logged this as a bug to SideFX,

Hey, why are you doing separate renders for your channels. Its probably better to render them all in one go and then split them out later. The AOV's are generally a byproduct of the render, so it doesn't add that much extra time to your render in one go.

Your render times will be so much longer doing it this way.
Just my 2 cents

willh
Hey, why are you doing separate renders for your channels.

I did that because I discovered that Karma XPU does not support CryptoMatte, and also the Albedo pass doesn't come out on Karma XPU.
So if I want the benefit of a fast Karma XPU beauty pass, I'll have to do the others on Karma CPU.

I need the N and Albedo pass for for the Intel Denoiser and I also figured a Normal Pass with more pixel samples than the main render might be good.

Oh i see, sorry didnt realise you where using xpu for your main bty render. Have you tried a later build?

I haven't tried it on the newer builds. But I have searched the Changelogs on "XPU", and did not see any changes or bug fixes regarding CryptoMatte, or the Albedo pass.

I am still struggling with this error. Almost done with the tedious process of restarting the render every 0-6 frames,
BUT unfortunately did not include CryptoMatte. But at least I can denoise now.

I realize this is old but in case someone is searching for this problem, I was able to solve mine by setting "maximum threads" to 1. No change in rendering time since I'm using XPU. Very odd but at least I can render my sequences without it stopping every few frames with that error code. Hope it helps someone.

Note: This was an issue in 19.5 and 20. I didn't test if this "fix" worked in 19.5.

Torbjorn "Tobbe" Olsson
I realize this is old but in case someone is searching for this problem, I was able to solve mine by setting "maximum threads" to 1. No change in rendering time since I'm using XPU. Very odd but at least I can render my sequences without it stopping every few frames with that error code. Hope it helps someone.

Note: This was an issue in 19.5 and 20. I didn't test if this "fix" worked in 19.5.

Hello:
I would like ask where to find maximum threads, I can not find it, i used Houdini 20.

Thank you so much!

mdouentertainment

Torbjorn "Tobbe" Olsson
I realize this is old but in case someone is searching for this problem, I was able to solve mine by setting "maximum threads" to 1. No change in rendering time since I'm using XPU. Very odd but at least I can render my sequences without it stopping every few frames with that error code. Hope it helps someone.

Note: This was an issue in 19.5 and 20. I didn't test if this "fix" worked in 19.5.

Hello:
I would like ask where to find maximum threads, I can not find it, i used Houdini 20.

Thank you so much!

USD Render ROP/Output

Also, are you using an intel CPU, like i9-12900kf and up? There are issues with those CPUs. For some rare applications, you have to disable 1-2 threads (Intel Extreme Tuning Utility is a good tool for this). I suspect that this is why it worked for me to change the maximum threads. Maybe if you're building a computer, go with an AMD CPU. They have a larger cache which helps too but I'm not an expert when it comes to CPUs.

Torbjorn "Tobbe" Olsson
I realize this is old but in case someone is searching for this problem, I was able to solve mine by setting "maximum threads" to 1. No change in rendering time since I'm using XPU. Very odd but at least I can render my sequences without it stopping every few frames with that error code. Hope it helps someone.

Note: This was an issue in 19.5 and 20. I didn't test if this "fix" worked in 19.5.

You just saved me so much time. Still having this issue in 20.5, and changing maximum threads to '1' has fixed my constant crashing. Thank you!

rorymclean3D
You just saved me so much time. Still having this issue in 20.5, and changing maximum threads to '1' has fixed my constant crashing. Thank you!

I'm glad to hear that! I just came back to also mention that Intel's 13th and 14th generation CPUs have problems as the recommended voltage is too high causing instability. They blame the motherboard manufacturers, you can read up on it by googling it. I've come across a lot of people who are not aware of this. I use "Intel Extreme Tuning Utility" to lower the "Performance Core Ratio" and that makes CPU intensive software more stable. That's probably why setting the maximum threads to 1 helps (unless you have an AMD processor and then it's on SideFX's side).

托比昂·“托比”·奥尔森

rorymclean3D
You just saved me so much time. Still having this issue in 20.5, and changing maximum threads to '1' has fixed my constant crashing. Thank you!

I'm glad to hear that! I just came back to also mention that Intel's 13th and 14th generation CPUs have problems as the recommended voltage is too high causing instability. They blame the motherboard manufacturers, you can read up on it by googling it. I've come across a lot of people who are not aware of this. I use "Intel Extreme Tuning Utility" to lower the "Performance Core Ratio" and that makes CPU intensive software more stable. That's probably why setting the maximum threads to 1 helps (unless you have an AMD processor and then it's on SideFX's side).

It seems that this issue has nothing to do with the CPU. I also have an AMD CPU and have encountered this problem.