Why Rhino continues to accumulate memory?


#1

Example: Work with 4 open files (300, 1200MB around) Why Rhino accumulates memory while working up to slow dramatically due to the exhaustion of the ram and the only way to resume the operations exit Rhino and restart your Mac?
It should not be enough to close the models? At most close Rhino?


(Marlin Prowell) #2

Post your Rhino info?


#3

Hi @marlin
Of course. Here is the Software information.

Software versions
Rhinoceros version: 5.4 WIP (5E12w)
IronPython version: 5.1.2015.131
WIP expiration: 11 marzo 2017
Language: it (MacOS default)
macOS version: Versione 10.11.6 (Build 15G1217)

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

Third party kernel extensions
com.logitech.manager.kernel.driver (6.40.1) C1D41FB7-7A01-38E3-A769-65B1DE65B0FD
com.3dconnexion.driver (10.4.2) D1FC94C5-936D-3185-BECD-5AEA40D01AEC
com.kairos.driver.DuetDisplay (2) ACE0314B-69A7-3100-9155-3B4B6C96B2EC

Hardware information

Computer hardware
Hardware model: iMac13,2
Processor: Intel Core i5-3470 CPU @ 3.20GHz
Memory: 32 GB
Architecture: Intel 64 bit

Video hardware
Graphics: NVIDIA GeForce GTX 680MX 2048 MB
Memory: 2048 MB
Screen size: 2560 x 1440
Displays: iMac (109dpi 1x)

USB devices
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Bluetooth USB Host Controller
Inateck USB to SATA3 Bridge: Inateck Generic USB Device
Lexar: WorkflowD512
TOSHIBA: External USB 3.0
3Dconnexion: SpaceMouse Pro

Bluetooth devices
Sconosciuto:
Apple: Apple Wireless Keyboard
Apple: Apple Wireless Trackpad

OpenGL information

OpenGL software
OpenGL version: 2.1 NVIDIA-10.10.14 310.42.25f02
Render version: 2.1
Shading language: 1.20
Maximum texture size: 16384 x 16384
Z-buffer depth: 24 bit
Maximum viewport size: 16384 x 16384

Implementation settings
Use texture compression: Yes

Appearance settings
Antialiasing: 2x
Mip map filtering: Nessuno
Anisotropic filtering: Nessuno


(Marlin Prowell) #4

A post was merged into an existing topic: High CPU usage in Mac Rhino


High CPU usage in Mac Rhino
(Marlin Prowell) #5

There was a problem with 5E7w and 5.3 where the storage used for a model was not released when the model was closed. That issue is fixed in 5E12w and 5.3.1. We do not know of any memory usage issues in 5E12w which you are running, nor do we see any memory issues running 5E12w. Closing a model and/or closing Rhino will free up the memory used.

Can you provide a model and detailed instructions for us to duplicate the memory issue you are seeing?


#6

Unfortunately I can not provide any of the models that have led to the problem. I can say is that rhino is still consuming memory during the work sessions. the first signs of a slowdown are highlighted with the inability to copy and paste into a new part files larger models. the closing and reopening of rhino of course allows you to free up memory, but I noticed that a reboot improves Rhino’s performance. 32gb of RAM is the maximum supported by the iMac. For this, I have no way of improving performance in these cases.


(Pascal Golay) #7

Hi Simon - as you may know you can send confidential files to tech@mcneel.com if they cannot be posted here on the public forum.

-Pascal


#8

I know, but unfortunately in this case it is not possible. For the moment they are forced to close Rhino and restart your iMac to continue working. Maybe (unfortunately), I simply reached the maximum threshold of working iMac / Rhino.


(Dan Belcher) #9

Hi Simon-

Unless we can submit the model, there’s little we can do.

-Dan


#10

I am aware. It is not very constructive my post, so I’m thinking of a way to play my problem with other files.