Another Rhino 8 WIP freeze

This latest beta is very unstable.
I use daily Rhino 8 WIP but with the latest updates now it freezes very often on random operations.
I have to kill the app from the task manager.
Within the past betas Rhino 8 WIP crashed only selecting the panels, now it hangs randomly.

Can you send me the SystemInfo of the machine you’re testing this on?

Rhino 8 SR0 2023-8-29 (Rhino WIP, 8.0.23241.14305, Git hash:master @ b9c7c5d6c30a8571a25d3d2a67b311501043ea51)
License type: Commerciale, build 2023-08-29
License details: Cloud Zoo
Expires on: 2023-10-13

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 96Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: AMD Radeon Pro 580X (AMD) Memory: 8GB, Driver date: 5-12-2023 (M-D-Y). OpenGL Ver: 4.6.14761 Compatibility Profile Context FireGL 21.30.44.18 30.0.13044.18017
> Accelerated graphics device with 7 adapter port(s)
- Windows Main Display attached to adapter port #0

Secondary graphics devices.
NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 8-4-2023 (M-D-Y).
> Accelerated graphics device with 8 adapter port(s)
- There are no monitors attached to this device!
NVIDIA GeForce GTX 1080 Ti (NVidia) Memory: 11GB, Driver date: 8-4-2023 (M-D-Y).
> Accelerated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!
NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 8-4-2023 (M-D-Y).
> Accelerated graphics device with 0 adapter port(s)
- There are no monitors attached to this device!

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: ATI Technologies Inc.
Render version: 4.6
Shading Language: 4.60
Driver Date: 5-12-2023
Driver Version: 30.0.13044.18017
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 8 GB

Rhino plugins that do not ship with Rhino
C:\Users\gabriele\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
C:\Users\gabriele\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\IntelDenoiser\0.6.4\IntelDenoiser.Windows.rhp “IntelDenoiser.Windows” 0.6.4.0
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.2.1.0
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V8\VRayForRhino.rhp “V-Ray for Rhino”

Rhino plugins that ship with Rhino
D:\Rhino 8 WIP\Plug-ins\Commands.rhp “Commands” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
D:\Rhino 8 WIP\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
D:\Rhino 8 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
D:\Rhino 8 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
D:\Rhino 8 WIP\Plug-ins\MeshCommands.rhp “MeshCommands” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.0.23241.14305
D:\Rhino 8 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
D:\Rhino 8 WIP\Plug-ins\Displacement.rhp “Displacement”
D:\Rhino 8 WIP\Plug-ins\SectionTools.rhp “SectionTools”

Not that this is the issue (I’m still processing the dump file)… But I’m just curious as to why you’re using this GPU as the primary display?

-J

Hi @gabrielefx,

Looking at the dump file you provided (thanks), there’s not a lot making sense atm. It appears that Rhino is trying to “exit” by certain plugin unhandled exception handling, and that it’s all in the managed (.NET) code.

I don’t really have any ideas atm, other than trying this:

  1. Start Rhino
  2. Run SetDotNetRuntime and set the Runtime=NETFramework
  3. Click OK to close the dialog box that will appear.
  4. Close Rhino
  5. Start Rhino again and see if you can still get Rhino to hang.

If Rhino still hangs, then I’m going to want another forced dump file (sorry), to see if it shows anything different or if it shows the exact same thing as the previous dump file. Also, any and all steps you can remember that lead up to Rhino hanging could help provide additional clues.

Thanks,
-Jeff

It’s a Mac Pro 7.1
I use it with both operating systems, MacOS and Windows.
The primary gpu is the AMD 580X Pro, then there are two internal Nvidia RTX2080Tis plugged on pci-x slots plus an external GTX1080Ti connected through a thundebolt 3 cable.
The monitor is connected to the AMD gpu through a TB3 cable.
The main reason to use a not Nvidia gpu it’s because I have all 11GB vram dedicated to the rendering engines: Vray (gpu) for Rhinoceros and 3ds Max, Fstorm for 3ds Max.
With this configuration, during the rendering tasks, the framebuffer is not affected by the rendering process, which, generally, slows down the viewport. Using a gpu dedicated to the framebuffer and viewports and one only for the gpu (cuda) render, it’s the best possible configuration for workstations.
This is not valid for software like D5 and Twinmotion.

Hi @gabrielefx

Did you bother to try my suggestion above?

Just curious if it made any difference. The crashes you keep sending are all the same, and appear to be DotNet related, and may have to do with resource management.

-J

Thank you for the crash reports @gabrielefx. We think we found and fixed the issue so with a little luck tomorrow’s WIP will be much more stable for you.

1 Like