RhinoBETA (not responding) - Beachball after switching back to Rhino

Serengeti (Rhino BETA)
1

Observation and serious impediment. More often than not, I find Rhino “not responding” switching back to open files. Only way out is to force quit and restart. You should see several crash (force quit) reports from my machine. This is not new, happens to me for several months or even since I use Rhino 9 WIP, got kinda used to it, would be great if this could be investigated.

It is especially frustrating, when I have a file open and prepared to share – switch application to Rhino – and then it won’t work and we are starring at a beachball. Not great a advertisement for Rhino (I know it’s beta)

Steps to reproduce:

  • Open and work on a file
  • Switch to other applications and go about your day
  • Switch back to rhino after a while

Expected:

  • Pick up work where I left it

Observed:

  • MacOS Beachball of Death. Force Quit dialog shows RhinoBETA (not responding)
  • Never really recovers even after 5min of waiting.

CleanShot 2026-08-31 at 11.01.13@2x
CleanShot 2026-08-31 at 11.01.13@2x892×850 33.5 KB

SysInfo_FSP_260831.txt (5.3 KB)

2

I haven’t seen this behavior and always have multiple files open. What particular workflows do you use in said files? Rendering, GH?

3

In most cases regular modelling, often for concept illustrations. Importing STEP files from partners, and meshes from the web. Nothing super demanding really. I notice that everything slows down with big files, but just encountered the issue with one very simple file open. Rarely, I use Raytraced or Grasshopper, but it happens constantly also without.

Thinking what might be special for my setup:

  • LAN zoo server, requires company VPN
  • I checked and see the “not responding behavior” also with an active VPN connection
  • Regularly the files I work on are on MS Sharepoint, synced to my hard drive
    • Sharepoint support on-demand sync, so either the file is on the hard drive, or it is downloaded when you try to open it.
    • Hypothesis: OneDrive (the Sharepoint app ?) decides that it is no longer worth keeping the file on the hard drive. When I switch back to the file, it tries to download it again from the cloud and chokes on it. Wild guess though.
4

Great information, thanks.

Lets get a DMP the next time you are in a unresponsive state.

When uploading (instruction 6) please put a link to this thread in the comments.

5

Hi Frank -

The public version that should become available tonight has a fix that should help in this situation. As this behavior is not something that we’ve been able to reproduce on our machines, I can’t verify if this actually fixes things. Please update to the newer version tomorrow and let us know if you are still running into this beach balling or not.
-wim

8

Did not run into this issue for a week, now I encountered it again.

2 files open, switched back to Rhino → beachball, waited for 10min now (I don’t think it’s coming back…)

Created and uploaded a Spindump.