Hello everyone,
I’d like to propose a feature that I believe would benefit every Grasshopper user who has ever been stuck in an endless computation loop.
It often happens that you accidentally graft the wrong dataset, which can lead to Grasshopper endlessly trying to process massive data structures, like culling millions of lists for duplicates, or similar mistakes that lock up the canvas.
It would be great if Grasshopper could detect (there is a timer running on a different cpu core, to not cause any bottlenecks) when a component has been running for an excessive amount of time (for example, more than 2 minutes) and automatically cancels the calculation, locking the canvas to prevent further freezing. Ideally, this timeout duration could be user-adjustable (e.g., 5, 10, 20 minutes, or “never”).
This feature could be tucked away in the settings so that beginners don’t get confused if their definitions stop after a few minutes without knowing why.
I think this would be a small but meaningful quality-of-life improvement for many users.
After all, we’ve all been there… no matter how experienced we are.
Who agrees or maybe has some other options/ideas for this feature?
All the best,
Alex