Rhino 7 closes without any error message when rendering

[nathanletwory (Nathan 'jesterKing' Letwory)]

@j.cpritchard

The first problem I had was running with a rendered view in Rhino v7 with just the AMD card it would sometimes throw up a small window that said something similar to ‘Server is busy’ with a greyed out button and a ‘switch to …’ button.

Sounds like you’re switching to the Raytraced mode, not Rendered.

When using the Radeon 5700xt please try:

Crash when scrolling through render settings

It seems compiling of kernels isn’t going as expected in thumbnail preview rendering. With the rendering panel hidden set the render device back to your GPU. Then change a viewport to Raytraced and click the running number in the right side of the HUD, change the number to something large, I use generally 999999 for this step. Let Rhino run for 10-20 minutes. You’ll see that after a short while the viewport changes to gray, that is expected. After the long wait change the viewport to Wireframe…

from the thread you linked.

@j.cpritchard

. . that’s also my explanation for having a possibly slightly odd combination of graphics cards.

Odd combination is fine. I have in my desktop: Radeon Pro WX9100 and Nvidia RTX A6000.

@j.cpritchard

C:\Users\Jon\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\AMDDenoiser\0.4.1\AMDDenoiser.Windows.rhp “AMDDenoiser.Windows” 0.4.1.0
C:\Users\Jon\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.0\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.0.0

If you’re running the denoisers while in the Raytraced mode - we’re currently leaking memory and it is being worked. So for now while Raytracing and you keep doing that for extended time turn off the denoiser.

@j.cpritchard

I also tried CPU rendering in cycles, which worked better, but the 5700xt’s memory usage still rises until it hits 8Gb and the system RAM now rises to 98% then drops to 74% and repeats the cycle a couple of times before crashing in the same way, with a spike in both GPU’s usage and Rhino disappearing at the same moment.

The GPU RAM isn’t used for this particular part, so it sounds a bit odd that GPU consumption keeps creeping up.

If you could please share your (simple) test file with me via https://rhino3d.com/upload?to=nathan@mcneel.com that’d be great. All weekend I’ve been working on different memory management fixes for Raytraced, so an extra file from a user to test with is only better.