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 David Rutten on May 14, 2015 at 12:47pm

I do not know. Are you loading a file or does Grasshopper just sit there doing nothing? Are any non-standard plugins loaded?

Permalink Reply by Jason Hare on May 14, 2015 at 1:18pm

No grasshopper file being loaded. Grasshopper is just sitting there chewing away on memory.

Plugins loaded:

1) Kangaroo

2) Starling 0.2

3) ghpython

4) WeaverBird

I deleted/uninstalled all plugins, re-installed Grasshopper v0.090076 and restarted my computer.Once I launch grasshopper again the same problem persists.

Permalink Reply by David Rutten on May 14, 2015 at 1:21pm

That's certainly novel... Can you start Rhino, then only run the GrasshopperDeveloperSettings command? I'd like to know if memory is also leaking when the main window hasn't been loaded.

Also what versions of Rhino and GH are you running specifically?

Oh and another test that might be informative, start Rhino and GH with no internet connection. Still leaking memory?

Permalink Reply by Jason Hare on May 14, 2015 at 1:30pm

The memory is stable when the GrasshopperDeveloperSettings is loaded.

I unplugged the Ethernet cable (no wireless service available) still leaking memory.

Grasshopper 0.9.76.0

Rhino V5 SR11 64bit (5.11.50226.17195)

hmmmm...interesting.

Permalink Reply by David Rutten on May 14, 2015 at 2:21pm

Well, we've ruled out the version checker (which would have been an easy fix), we've ruled out plug-ins (so the fault is definitely with McNeel), we've ruled out the Rhino plugin manager (narrowing it down from McNeel generally to me specifically) and I'm beginning to run out of ideas.

You've had some plugins installed, does that mean you've been using GH successfully for a while before this problem started happening?

Permalink Reply by Jason Hare on May 14, 2015 at 3:33pm

I resolved it....

I followed the path to where GH was installed. Deleted all the program files. Then re-installed GH. Funny thing once I re-installed GH the file path changed in the rhino plugin manager. I am working on a computer with multiple network users, I may have selected the 'just me' option when I first installed GH a few months back. We have 13 mirrored computers so I don't always get around to each on a regular basis to see how well they are running.

thanks for the help David.

Permalink Reply by David Rutten on May 14, 2015 at 3:42pm

Glad it got fixed, but I would love to know what caused it. I suspect we will never know.

Permalink Reply by Daniel on May 9, 2016 at 6:44am

I am experiencing similar problems but do not know what is causing the problem.

I have windows 7 64bit and 32Gb of physical memory. I am using Grasshopper v0.9.0076 in Rhino 5 SR12 64-bit. When I open rhino but not grasshopper, the memory is stable around 176,660K. Once I open grasshopper but do not open any projects the memory begins to increase at a fast rate until it stabilises around 13GB. This is prohibitive when I start opening grasshopper projects and other applications.

I have the following plugins (they haven't changed for about 5 months):

kangaroo
kangaroo2
lunchbox
TT toolbox
excelreadwrite
hoposnake
smart form

Things I have done:

I've tried no internet which did not help. I have reinstalled Rhino but left the grasshopper files remain the same, this did not help. I opened the developer setting command only and there was no memory problems. I then found the path to where Grasshopper was installed, deleted all the files and reinstalled with all plugins. This solved the issue, or at least temporarily.

I then opened the Grasshopper file and after saving, restarting the computer and starting back up again, the memory run-away problem is back, prior to opening any files.

I don't know what is causing this reoccurring problem and at what end it sits. Any help is greatly appreciated.

Daniel

Permalink Reply by Daniel on May 9, 2016 at 7:09am

An interesting development. I notice that when I open a Grasshopper file, the memory drops and gradually increases until the file opens. The screenshot shows grasshopper stable at 13GB with no file open and then (marked by the "X") once the file opens the memory drops. At least the memory does not continue to run away.

Permalink Reply by Julian Buhagiar on April 4, 2017 at 3:29am

I have started experiencing the same phenomenon.

It was ok about 2 weeks ago, but something somewhere seems to have changed and now is unoperable.

UPDATE....

A reinstall didn't work initially, but as the feedback above says....delete the install path from the common files before a reinstall appears to resolves the issue.

Permalink Reply by David Rutten on April 6, 2017 at 1:38pm

There's a YouTrack item for this now. I'm out all next week but when I get back this will be priority #1, unless I get overruled by Seattle HQ.

Permalink Reply by Scott Overall on April 10, 2017 at 10:31pm

I just started running into this problem also.

The symptoms I am seeing are grasshopper hanging on first launch and chewing up a lot of memory. Memory usage sits stable for a bit after opening, but when I close Rhino, the Rhino process doesn't close in the task manager and starts eating up more and more memory until all of the computer's memory is being used. This doesn't happen when I close Rhino without ever opening grasshopper.

I haven't installed any grasshopper plugins in the last week, but I have installed the Iray and Octane Rhino plugins and deleted the FireRender plugin files from the common folder and the roaming folder. I don't know if this is related, but it is the only change I have made since I have started seeing these problems.