Hi guys, I often read in assemblies, turn on custom rendermesh and extracts it, delete the originals and joins up meshes to make light files to reference into projects. And after deleting all the originals I want to purge them from the file, but purging can be veeery slow. (While exporting the new meshes are done very fast)
Any idea what causes this?
I run in this situation too and missed an ESC functionality, because I thought, if I could stop the long slow process, than could I save the file before and I try it again, not that it crashs now.
I often terminate Rhino and do it from scratch again… less painful than having to wait for an unknown length of time 
Hi Jorgen - I’ll see if I can reproduce this - roughly how many block definitions are there? My guess of the moment is that it may be as much the nesting of blocks as the sheer number.
-Pascal
Same here, often purging files with 1000s of unused definitions takes very long, with no sign of progress of ability to cancel/escape. It would be great to at least get some feedback if coffee break is in order, or ability to cancel, if speedup is not likely.
thanks,
–jarek
There must be more to it… I made 1000 different blocks, deleted the instances, and Purge was instant…
-Pascal
hi @pascal, there could be more to it - maybe 10s of 1000s of blocks, too. It’s common when bringing in Revit models saved as DWG where each element is a unique block instance. Next time I can try to provide a sample file.
thanks,
–jarek
Hi Jarek - thanks - I wonder if these are also deeply nested, perhaps. Not sure it matters, but I can imagine that might slow down the checking.
-Pascal
Sorry for the bump, but I have the same issue. Would be interested to know if there is any progress made on figuring this out
Hi - it doesn’t look like we received a reproducible sample for this issue. Can you provide a file?
-wim