Rhino Freezing entire Mac suddenly

Hi!

I have been experiencing a recurring problem since I updated my Macbook pro to OS Catalina 10.15.4.
What happens is that my computer completely freezes- as if it has been shut off, but with the display still on. The forcetouch on the trackpad stops responding, the keyboard light goes off, etc. This happens suddenly, in different files (both light and heavy) and does not seem to have a correlation with any specific commands. I get no slowing down or any indication that it is about to happen.

I have urgent deadlines and no access to another computer thanks to COVID, please help!
Regards,
Sahar

Rhino 6 SR25 2020-4-23 (Public Build, 6.25.20114.03572, Git hash:master @ f35d7ded15ec317635ced435d8df84327397038d)
License type: Evaluation, build 2020-04-23
License details: Cloud Zoo. In use by: Sahar ()
Expires on: 4369418-01-06

Apple Intel 64-bit macOS Version 10.15.4 (Build 19E287) (Physical RAM: 8Gb)
Mac Model Identifier: MacBookPro12,1
Machine name: JARVIS
Language: en-GB (MacOS default)

Intel® Iris™ Graphics 6100 (OpenGL ver:4.1 INTEL-14.5.22)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: None
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: Intel Inc.
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: n/a
Maximum Viewport size: 16384 x 16384
Total Video Memory: 1536 MB
Graphics: Intel Iris Graphics 6100
Displays: Color LCD (298dpi 2x)

Graphics processors
Intel Iris Graphics 6100 (1536 MB)
Color LCD (1680 x 1050)

USB devices
Broadcom Corp.: Bluetooth USB Host Controller
MOSART Semi.: 2.4G Wireless Mouse

Bluetooth devices
None

Third party kernel extensions
None

Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftFoundation.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswiftCryptoTokenKit.dylib
/usr/lib/swift/libswiftos.dylib
/usr/local/cuda/lib/libcuda.dylib
/Library/Frameworks/CUDA.framework/Versions/A/CUDA
/usr/lib/log/liblog_network.dylib

Rhino plugins
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 6.25.20114.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 6.25.20114.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 6.25.20114.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/PlugIns/Displacement.rhp “Displacement” 6.25.20114.1002
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/BlockEdit.rhp “BlockEdit” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 6.25.20114.3572
/Applications/Rhinoceros 2.app/Contents/PlugIns/RhinoRender.rhp “Rhino Render” 6.25.20114.1002

I suggest taking your mac to the apple store when it reopens or ask for online assistance from them. This sounds like like a system problem.

Unless there are Kernel Mode Kommandos programming at McNeel, what you are describing would have to be an operating system bug or a hardware problem.

I don’t see any obvious problems in your SystemInfo other than you Mac is getting pretty long in the tooth.
We are seeing a few reports of problems with these older Intel 6000 and 6100 Macs running under powered GPUs.
Your MBP is 5+ years old now so my guess is things are not going to improve going forward.

Sorry.