Open FalconStarFighter opened 2 years ago
@FalconStarFighter Did you have a huge dataset there? If so, Dynamo probably crashed when it ran out of memory allocation. We have improved this exact scenario in Dynamo 2.13: https://dynamobim.org/dynamo-core-2-13-release-part-3-3/
Issue Description
I accidently set a "get item at index" to both the item and the index and it froze up on me. Bummer that a bad flick of the wrist crashed my machine because I couldn't kill the command when dynamo is set to automatically run
Dynamo version
Dynamo:
2.12.0.5650
Operating system
OS:
Microsoft Windows NT 10.0.19043.0
What did you do?
I accidently set a "get item at index" to both the item and the index and it froze up on me. Bummer that a bad flick of the wrist crashed my machine because I couldn't kill the command when dynamo is set to automatically run. I was hoping it would time out with an error, but instead it crashed.
What did you expect to see?
I expected to see a crash as soon as it started, but I wished there was a way to kill the script as soon as it happened.
What did you see instead?
A crash
What packages or external references (if any) were used?
Clockwork
Stack Trace
CLR:
4.0.30319.42000