Components that call functions in parallel on Rhino.Geometry.Brep can cause startup errors in certain situations, causing a System.AccessViolationException to be thrown in external code (in RhinoCommon.dll. This not only causes Grasshopper to crash, but nukes the whole Rhino application immediately, which is unacceptable under any circumstances. While a bug report has been submitted to McNeel, this seems like an underlying issue with race conditions in the Brep class in general.
Of course, meshes provide a more performant alternative to Breps for most Grasshopper use-cases, so this (hopefully!) does not represent a large loss of functionality.
Components that call functions in parallel on
Rhino.Geometry.Brepcan cause startup errors in certain situations, causing aSystem.AccessViolationExceptionto be thrown in external code (inRhinoCommon.dll. This not only causes Grasshopper to crash, but nukes the whole Rhino application immediately, which is unacceptable under any circumstances. While a bug report has been submitted to McNeel, this seems like an underlying issue with race conditions in theBrepclass in general.Of course, meshes provide a more performant alternative to Breps for most Grasshopper use-cases, so this (hopefully!) does not represent a large loss of functionality.