Cluster crushed Rhino when a slider input changes rapidly.

This is a question for developers.

I know that the clusters still have problems, but I want to consult why this happens and if there is any solution.

I have a cluster with multiple inputs with sliders. When I change the value slowly, so good, but when I do it quickly, rhino crashed.

Attached file so they can check it.

Is it a problem of cluster object? Or my definition? Could be some kind of gap in the data inputs of a component becomes too unstable? If so, could be solved with some type of gate?

Thank you.

Attachments:

ProblemClusterCrashed.gh, 208 KB

Replies to This Discussion

Permalink Reply by David Rutten on November 7, 2014 at 2:09pm

A crash always means it's our fault, users should not be able to crash software in an ideal world.

I can repeat the crash and I get the following .NET call stack:

System::AppDomain::CurrentDomain->UnhandledException event occured

SENDER: Name:DefaultDomain
There are no context policies.

EXCEPTION: System.Runtime.InteropServices.SEHException
MESSAGE: External component has thrown an exception.
SOURCE: RhinoCommon
CALL STACK
at UnsafeNativeMethods.CRhCmnUserData_Delete(IntPtr pUserData, Boolean only_if_no_parent)
at Rhino.DocObjects.Custom.UserData.Dispose(Boolean disposing)
at Rhino.DocObjects.Custom.UserData.Finalize()

Do you also see a crash reporting window? If so, please always send in the reports, they are all collected and organised on our YouTrack system.

Permalink Reply by Daniel González Abalde on November 7, 2014 at 2:54pm

Thanks David, sorry but I can not post a comment with the dump file: S I dont know why...
Can you give me some advice from your experience to fix my cluster? Or is it an absolute binary mystery? ;P Do I have any other option than to remake the definition with other logic-components? Do you think I should do trial and error or you have some better idea?

Permalink Reply by David Rutten on November 7, 2014 at 4:21pm

It seems to be a bug in RhinoCommon, some sort of memory issue. Either we're disposing stuff too early, or in the wrong order, or perhaps it's even going wrong in the C++ part of Rhino. I'm afraid it's too far down for me to figure out.

I can offer no solutions, I'll have to put the bug on YouTrack and we'll see what Steve has to say about it.

Permalink Reply by Daniel González Abalde on November 7, 2014 at 4:56pm

Ok, something I will do to make it work.

Thank you very much for your assistance David :D

Permalink Reply by Todor Todorov on January 30, 2015 at 8:39am

Hi Daniel,

I have the same problem. I am running an automation that render with vray frames of animation. But rhino crashes every time at a different frame because of the animation slider.

I want to ask you if you have solved the problem and how.

Thank you in advance

RSS