Grasshopper Display Error

I keep getting the following messages:

"An exception was thrown inside the drawing pipeline:

Source: System.Drawing

Type: Exception of type 'System.OutOfMemoryExecption' was thrown.

The display of objects will be disabled to prevent this from happening again. Please save . . [yada yada yada]"

and

"An exception was thrown inside the drawing pipeline:

Object: Group

Source: mscorlib

Type: Exception of type 'System.OutOfMemoryExecption' was thrown.

The Grasshopper display routines have gone into ultra-paranoid mode in a last-ditch attempt to minimize damage. One or more objects will probably be drawn as blank rectangles with error message.

Display performance might be affected for this session."

Then grasshopper turns completely red and sometimes rhino crashes. I didn't change anything in the definition when this started happening. I was working on another file and when I returned to it I got the display error. I've been able to isolate the components causing the problem, I haven't fixed it yet, but I assume that I can work it out. I have various grasshopper plugins installed: geco, gHowl, DIVA, Local Code, and Hoop Snake. In the grasshopper definition that is generating the error, I'm only using geco, and all geco components are disabled when I get the error. I've never seen this before and I'm curious if anyone knows what is going on. I found a similar error in this post. Thanks.

Replies to This Discussion

Permalink Reply by Luc Wilson on May 3, 2012 at 3:25pm

It turns out that it is a rotate component that is causing the error. I get the error when rotate is creating 6,317,325 lines. I reduced the number of lines to 1,546,125 and the definition works just fine, calculating the solution in only 2 seconds.

Permalink Reply by Luc Wilson on May 4, 2012 at 2:36pm

I'm no longer getting the "Grasshopper display error," but now some components are giving me the following error:

Error: Exception of type

'System.OutOfMemoryException' was thrown.

Permalink Reply by David Rutten on May 4, 2012 at 2:58pm

Hi Luc,

maybe you really are running out of memory. Can you check in the task manager how many Megabytes Rhino is consuming? Do you have access to Rhino5 64-bit? If yes, can you test again, see if it fares any better?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by nathan shirley on May 3, 2017 at 5:34pm

Hi David,

I'm having the same issue that Luc first had with the same messages and red screeen, the only change I made around the time of the error starting was that I changed my rhino license file, but I can't see how that would cause an issue. I checked my memory usage via task manager, it does spike a little when I open the file, but doesn't seem to max out.

I'm not able to trouble shoot the file, since I can't see it. so I'm pretty stuck.

I've got weeks invested into this file, and all of my backups all started behaving the same way.

any help would be greatly appreciated!

Thank you,

Nate

Attachments:

red screen.gh, 1.2 MB

Permalink Reply by David Rutten on May 4, 2017 at 3:00am

Whoa... that is one, erm, big file. Due to what I assume is a Food4Rhino malfunction I couldn't download the Advanced Surface Tools, so your file opened only partially, but it does not result in any errors. Although obviously there are problems with the display:

Those gradients on the components are misaligned. The stuff is so far away from the origin that the floating point numbers used to describe the visual elements have come undone. I do not know whether this ultimately causes the errors on your machine, but it might be a good idea to compactify your component layout a bit.

Also does this file contain four separate copies of that one giant network? Probably a good idea to put those into disjoint files.

As soon as I can load your file the way it was intended, i.e. as soon as I manage to install Advanced Surface Tools, I can do some of this work over here.

Permalink Reply by David Rutten on May 4, 2017 at 3:12am

Well, with ASTools installed the file crashes instanly on load. Not a red screen, just a straight up crash without even a .NET call stack.

Perhaps you should try disabling the solver, and only then opening the file. Does it still fail in that case?

Permalink Reply by nathan shirley on May 4, 2017 at 5:11pm

Thanks for the quick response David! As is evidently obvious form my massive file, I'm an enthusiastic noob, with only a few months using rhino. The file is basically the same network copied four times and linked to some shared sliders, then that cluster is copied four additional times. I can run the 4 clusters as separate files if needed, but the point of the file is to compare and contrast different form families in real time. It was actually working beautifully, and then one day it just stopped working.

I tried disabling the solver, but the errors are the same. (I've attached screenshots of each). I've managed to get an older version of the file working from before I copied the larger network 4 times. but I'm hoping to eventually get to the same point again.

I'll try "compactifying" everything before copying, which I assume means condensing it within the grasshopper work space (?).

any further insight or tips would be appreciated. Thanks for your time, and an amazing tool.

Attachments: