This is my guess, I’m not 100% sure this is correct - but maybe this reply will help others trying to debug why Rhino crashes in relation to applications using libiomp5md.dll. Which can cause trouble for plugin developers as they are not in control of what other applications has done to your machine.
So those dlls will take precedence over any plugins dlls. This is the case for Anaconda (python) for instance. Some other programs may also set their installation folder in system PATH (or copy their dlls to C:/Windows/), which will load the dlls into memory before Rhino/Grasshopper get a chance to load anything.
So if grasshopper is loading Evolute before karamba then karamba will try to use the libiomp5md.dll version that ships with Evolute. Rhino/Grasshopper will load the dlls in the installation folder, and the nature of dll is that windows only loads one of the libraries into memory so that the methods can be shared by different consuming applications. This scripting guide comes with a help-file ( Karamba3D133SDKDoc.chm also accessible online Karamba3D 1.3.3 SDK Documentation ) which covers karambaCommon.
karamba.gha connects GH to karambaCommon.dll and takes care of the graphical user- interface. I believe this is caused by a dll clash, the two applications use different versions of libiomp5md.dll. ) and is therefore independent from Grasshopper or Rhino.
