If I use the drop down menu to replace an object, it works, but it leaves behind a tmp object of the object that has been replaced on top of the update:
In order to get it to go away I have to hit undo -- which means I also have to do something like move an object to create something to undo that won't affect work I am doing.
Didn't see anyone else reporting this, so thought I should share.
At some point I got some of those tmp objects too.
The way I got the tmp objects was if I embed an object and then undo. After undo then there will be an extra empty tmp object behind the original object.
But haven't tried getting one the way you describe here.
@spacelordmother could it, in your case, have to do with the undo function too?
Or are they there before you do the first undo step?
In my case they are generated by the replace or embed. Then I have to undo to get them to disappear— can’t select them, so can’t delete them.