ObjectDisposedException on closing C# script component

Hi,
has anyone of you got a similar RhinoDotNetCrash.txt output? Im facing this Problem now for some months. It happens only some times. When i change code on an ordinary c# component and confirm it with the OK button on the editing Dialog, Rhinoceros crashes.

Cheers,
FF

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

SENDER: Name:DefaultDomain
Keine Kontextrichtlinien vorhanden.

EXCEPTION: System.ObjectDisposedException
MESSAGE: Auf das verworfene Objekt kann nicht zugegriffen werden.
Objektname: "GH_WndProcOverridenCodeEditor".
SOURCE: System.Windows.Forms
CALL STACK
bei System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
bei System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
bei QWhale.Editor.SyntaxEdit.QWhale.Common.IControl.Invoke(Delegate )
bei QWhale.Editor.TextSource.TextSource.BackgroundThread.Resume()
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Threading.ThreadHelper.ThreadStart()

Replies to This Discussion

Permalink Reply by David Rutten on March 12, 2016 at 5:02am

The problem is with the code editor we use (QWhale). I think* it has been fixed but we're not planning another release for Rhino5. If you have access to Rhino6 beta (which ships with Grasshopper) you could switch to that, it contains a number of bug fixes including this one.

* this is the most common crash report that people send in, but I haven't seen one happening on Rhino6 yet. But that's not really proof I managed to fix it; black swans and all that.

Permalink Reply by Florian Frank on March 12, 2016 at 9:05am

Hi David,

thank you for the quick reply.

sorry for the duplicate thread then. Indeed i have Rhino6 beta and it never happened there. I'm currently working on Rhinoceros 5 for a client project and so i came across this problem. I'll try to use Rhino6 as much as possible ;-)

Greetings from Innsbruck,

RSS