Run away physical memory when opening grasshopper

Might anyone know why when I open Grasshopper (v0.090076) the memory used by rhino 5.0 (64 bit) on Windows 7 64bit begins to runaway eventually freezing the computer in the span of around 1 minute. Once grasshopper and rhino are closed and rhino is re-opened, the memory usage returns to a stable 263,333K.

Any advice would be much appreciated.

best

Replies to This Discussion

Permalink Reply by Julian Buhagiar on April 11, 2017 at 1:56am

This is an overview of what's happening after a fresh install... It doesn't hang as frequently as before but the memory does run away still until it manages to dump it to disk.

Permalink Reply by Julian Buhagiar on April 11, 2017 at 3:38am

Video showing performance monitor in realtime alongside grasshopper...

Shows Rhino Loading @ 0:28 - memory stable

Grasshopper Loading @ 0:54 - memory begins to rise to 90%+

Adding components to canvas

Closing and creating a new file (memory resets when this is done) @4:00, 5:57, 6:53

System slow down and crashes @ 8:16 (takes 5 minutes to end the process - perhaps not the most entertaining movie to watch until the end - a good point to turn the kettle on)

Permalink Reply by Julian Buhagiar on April 11, 2017 at 5:29am

A repeat test this time showing a successful session of Grasshopper where memory stabilises following what appears to be memory dumps.

Video showing performance monitor in realtime alongside grasshopper...without a crash

Shows Rhino Loading @ 0:00 - memory stable

Grasshopper Loading @ 0:29 - memory begins to rise to 90%+

Memory dumped to disk after double click on canvas and stabilises @ 1:46

Place Pop 3D component @ 1:47
Close file - Memory runs away@ 2:56

repeat above steps double click doesn't dump this time whilst memory is on the rise. @ 3:09

memory dumps and stabilises after deleting a component @ 4:00

close file @ 4:29

Repeat with more geometry to try higher stress on CPU

Memory dump and stabilises with no corresponding GH interface actions. @ 6:13

Permalink Reply by Daniel on October 18, 2017 at 3:17am

I have eliminated the runaway memory issues following the advice to erase the MRU list. The extra step required to update the MRU setting was to save a GH file and then close rhino and restart GH.

Permalink Reply by Elijah Hughes on October 20, 2017 at 2:42pm