My WIP copy nearly always say it had crushed upon CMD+Q

Rhino Rhino for Mac
1

Hello Dan
as the title say, nearly always when i close Rhino WIP , it thinks it has crashed… even when i update and relaunch it still report a crash, i have sent one [crash report] recently… there is never any damage to my work it is just strange but consistent behaviour, it has been like this for a while [through a few updates] initially i though it was bugs in GH but i get it also when GH is not opened.
maybe it has to do with some of the “not yet supported fully” GH add-ons i have tried?

Software information

Software versions
Rhinoceros version: 5.2 WIP (5C224w)
IronPython version: 5.1.2015.131
Language: en (MacOS default)
OS X version: Version 10.11.5 (Build 15F34)

Plug-ins
/Library/Frameworks/3DconnexionClient.framework/Versions/A/3DconnexionClient

Third party kernel extensions
com.3dconnexion.driver (10.2.5) 403007CA-7295-332E-9F17-DC3EA5DFD88D
com.rim.driver.BlackBerryUSBDriverInt (0.0.67) 3D68C30B-05F8-FB91-8606-B0F892DAA206
com.nvidia.CUDA (1.1.0) 5AFE550D-6361-3897-912D-897C13FF6983

Hardware information

Computer hardware
Hardware model: MacBookPro11,3
Processor: Intel Core i7-4960HQ CPU @ 2.60GHz
Memory: 16 GB
Architecture: Intel 64 bit

Video hardware
Graphics: NVIDIA GeForce GT 750M 2048 MB
Memory: 2048 MB
Screen size: 1440 x 900, 1920 x 1080
Displays: Color LCD (221dpi 2x), W2261 (102dpi 1x)

USB devices
Apple: Card Reader
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Inc.: Bluetooth USB Host Controller
3Dconnexion: SpaceNavigator for Notebooks

Bluetooth devices
Apple: Apple Magic Mouse

OpenGL information

OpenGL software
OpenGL version: 2.1 NVIDIA-10.10.10 310.42.25f01
Render version: 2.1
Shading language: 1.20
Maximum texture size: 16384 x 16384
Z-buffer depth: 24 bits
Maximum viewport size: 16384 x 16384

Implementation settings
Use texture compression: No

Appearance settings
Antialiasing: 4x
Mip map filtering: None
Anisotropic filtering: None

with thanks
akash

2

That seems like a good guess. To test the hypothesis, please remove those GH components that you have added (or just move them to the desktop) and see if Rhino stops crashing. If Rhino stops crashing after a Command+Q, then you can be reasonably certain that it was GH components. A better test to find the culprit is to use a “manual” binary search: move half of the potential offenders to the desktop - test Rhino - if it crashes, you know you need to test again. Repeat the same steps until you have isolated the offender.

Keep in mind, we’re not even close to fully supporting third-party components in ExplicitHistory. It is still “early days.”

Best of luck and please let me know what happens!
-Dan

3

Hi Dan
it looks like that weirdness went away.
i did removed one thing, MeshEdit.gha which anyways has been pulling a long list of missing stuff upon calling GH-ExHi. Yet it may well be one of the latest quick updates the fixed that, i can’t tell which.
many thanks.

akash