Colour wheel crashes file

Hi,

I just came across a problem when trying to open a file with a colour wheel that had disabled components upstream, makeing it read null values. I got the message below, then the canvas was completely red and grasshopper froze. However after trying a couple of times the file eventually opened so I could remove the wheel and resave my work.

"An exception was thrown inside the drawing pipeline:

Object: Colour Wheel

Source: System.Drawing

Type: Out of memory.

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 messages.

Display performance might be affected for this session."

This really made me nervous for some time before i managed to get acess to my work. Don't know why this only happened now, and never before. If this somehow interests you I can email the files but i rather not make them public at the moment.

Attachments:

GH-red.jpg, 187 KB

Replies to This Discussion

Permalink Reply by David Rutten on January 7, 2014 at 2:37am

Hi Carl,

I can't seem to replicate this by feeding a null into the Colour Wheel. Please do post a file (you can use the internalize menu option on a parameter to cut out everything in front of it). I also probably don't need anything after the colour wheel so you don't have to share that.

David Rutten

david@mcneel.com

Permalink Reply by Carl Christofferson on January 7, 2014 at 6:29pm

Here are the files.

It is very weird. If i start rhino and open the .gh it will sometimes turn the canvas red, and sometimes it will just display the warning but then continue as normal. It seems like it is most likely to turn red if the .3dm is not open.

Attachments: