hmm, I thought it could be an external cause I made a search for ".x%lx.c delete %lx
IN0" and couldn't find it, but it's there as ".x%lx.c delete %lxIN
%d" (oops!). Anyway, for what I see, the error could be triggered by any of the iemguis then. I also suspect the fix for this would be related to something I've already been doing in a PR ( see
https://github.com/pure-data/pure-data/pull/1079/commits/8ba3bd3b115d62dc8de6f93923fb3d64223fecc1 ). The reason is that I was dealing with a similar issue (exact same error, actually) in scope~ and fixed it with something like that.
So if you want you can send me the patch Eric, and I can try and debug it and see if my fix deals with this issue or if I have to expand it.
This could be triggered by the abstraction setting a receive name for the iemgui, so it tries to delete the inlets but it doesn't find it cause it is not visible and hasn't been drawn/created. See if you're doing that.