I have had several hangs in which the mouse becomes non-responsive system wide. After these occur, Rhino is dead. I can among other applications but mouse is click is disabled. I can move the mouse cursor but that is it. I have to use the power button to restart.
This has occurred several times but it is not frequent. But is is an annoyance when it happens.
I have not yet identified any common function that causes the problem. It always occurs while moving the mouse in the middle of a command. I have never see it occur as the rule of executing a command.
I know these are nearly impossible to diagnose at this level of information but I thought I would get it out there. Maybe others can fill in the blanks.
in the scenario you describe, the apple menu should still be active if you can switch out of rhino to other apps.
next time, try clicking on the apple menu (top-left )… then bring up the force quit dialog… you can try force quitting rhino to see if the cursor recovers.
This is not normal behavior. Rhino is remarkably stable for me. In general, I’ve only had two past instability problems. One related to micro-loops in a file and the other (recently) which Dan thinks may be related to duplicate fonts in my system folder. I don’t think in either case the problem was system-wide.
Incidentally, how big is your file?
I’d try the font cleanup advice here and email the file to McNee to see if they find anything.
@bigjimslade I suspect that this is a hardware problem. No application can lock up a machine. “But”, you say, “this only happens with Rhino!” Some Macs have two GPUs and Rhino will use the more capable one. OS X will run everything else with the integrated GPU. Perhaps you have a Mac like this and the discrete GPU has problems.
Post your Rhino info from About Rhinoceros > More Info > Copy to clipboard so we can see what kind of hardware you have.
Software versions
Rhinoceros version: 5.1 (5B161)
IronPython version: 5.1.2015.131
Language: en (MacOS default)
OS X version: Version 10.10.5 (Build 14F27)
Plug-ins
None
Third party kernel extensions
com.parallels.kext.usbconnect (10.3.0 29227)
com.parallels.kext.hypervisor (10.3.0 29227)
com.parallels.kext.netbridge (10.3.0 29227)
com.parallels.kext.vnic (10.3.0 29227)
Hardware information
Computer hardware
Hardware model: MacBookPro6,1
Processor: Intel Core i5 CPU M 540 @ 2.53GHz
Memory: 8 GB
Architecture: Intel 64 bit
Video hardware
Graphics: NVIDIA GeForce GT 330M 512 MB
Memory: 512 MB
Screen size: 1920 x 1200
Displays: Color LCD (133dpi 1x)
USB devices
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple Inc.: Bluetooth USB Host Controller
Apple Inc.: Built-in iSight
Apple Computer, Inc.: IR Receiver
Bluetooth devices
None
OpenGL information
OpenGL software
OpenGL version: 2.1 NVIDIA-10.0.35 310.90.10.05b12
Render version: 2.1
Shading language: 1.20
Maximum texture size: 8192 x 8192
Z-buffer depth: 24 bits
Maximum viewport size: 8192 x 8192
Implementation settings
Use texture compression: No
I don’t have good news. You have a Mac that can develop GPU problems and thus cause kernel panics. You can search for “macbookpro6,1 gpu” to find articles. This one describes the problem and a potential solution. You can install gfxCardStatus and force your Mac to always run the integrated GPU and never run the NVIDIA discrete GPU.
After you install gfxCardStatus, you will be able to see that OS X switches to the NVIDIA GPU when Rhino starts, and switches back to the integrated GPU when you quit Rhino. This is why Rhino seems to be the cause of the crashes.
With gfxCardStatus, you can force your computer to always use the NVIDIA GPU, and, if the NVIDIA GPU is the cause of these crashes, this should cause your computer to crash more often, even if Rhino is not running. Or, you can force your computer to always run on the integrated Intel HD graphics GPU. This GPU is not very good for OpenGL work which is what Rhino needs, so Rhino’s performance and capability will be diminished.
If you force your computer to use the integrated GPU, you can look in About Rhinoceros > More info… and check the Graphics: setting in the Hardware tab. It should say Intel HD Graphics or something similar.
I may have more information. It appears that this problem I discovered occurs as a result of the the Mac screen getting put into a bad state. I think now that I can get out of this hang by shifting screens (3 finger swipe) then shifting back to the screen with Rhino in it.
)… then bring up the force quit dialog… you can try force quitting rhino to see if the cursor recovers.