`compute.geometry` process often locked when developing in Visual Studio

image

When debugging Grasshopper Plugin in Visual Studio, and close / kill Rhino Process, the compute.geometry is often left out without being killed.

This creates problem when users want to start debuging again, as it blocks the re-written of new .gha files.

It seems after almost a year, this problem still exist.

To be specific, after I started a debug process and open Rhino from VS and do some work, when the process crashes or I kill it from VS, the Rhino process will be killed, but the compute.compute process will not.

As a result, I need to open the “Task Manager” and manually kill it.

This issue won’t happen 100% of the time, but from my experience, 60% - 80% of the time I need to do it.