GH crashing rhino/ & GH with a GDI error

I am consistently getting a crash from a GDI drawing error in Grasshopper. At this point it is definitely from trying to display "too much" information either in a panel or on hover over a component output that tries to show the same data. The panel safely contains the error without crashing. The on-hover behavior crashes both programs. The data itself is a very long string of points. Long, but nothing else to it. No recursion happening in a vb component or anything like that. Otherwise, the definition works fine.

Replies to This Discussion

Permalink Reply by Arend on December 21, 2010 at 12:59am

I can confirm this crash behaviour with custom components:

http://www.grasshopper3d.com/forum/topics/rhino-crash-on-invalid

My speculation is that there is no exception checking on the hover component, compared to the output that is being checked.

Permalink Reply by Matthew Gilbride on December 21, 2010 at 5:30am

Thanks! Thought I was going crazy here. Custom components means when using VB & C custom components or plug-ins? (AH-Just looked at your link and see its the VB / C components) I see no run-time errors,however and get this behavior on stock components downstream from custom components. I am ignoring invalid list entries while recomposing a triangular mesh. Thought those would be safely filtered out and not affect downstream behavior?

Permalink Reply by Arend on December 21, 2010 at 6:49am

Yes it's a custom plugin developed using rhino, can you share a definition that has these kinds of errors?

Permalink Reply by Matthew Gilbride on December 21, 2010 at 10:37am

Yep. This file will produce the error. Assign a mesh sphere by ref or with a primitive. I used a sphere with a lot of vertices. You will also need to define an output path for the text file output. GUI bogs down, the panel showing the output eventually errors out, and you have a good chance of crashing on hover over the output of one of the last components in the def. There are run-time warnings in the make mesh from scratch component. But no errors that I see. Maybe I'm missing something?

Attachments:

ErrorDef.gh, 38 KB

Permalink Reply by Matthew Gilbride on December 22, 2010 at 11:49pm

Any ideas on what is causing the error here?

Permalink Reply by Arend on December 23, 2010 at 12:07am

Which component is causing the crash?

Permalink Reply by Matthew Gilbride on December 23, 2010 at 12:24am

I get it in the last join component on over over the R output and is also seen in the panel showing the output from that same component. Use a sphere with a high vertex count and you should see the error. You should also notice the gui bogging down and become hard to pan about. I understand it's a lot of data, but should the gui be causing this crash?

RSS