While search for causes or reported memory clears on a coil tail out, we discovered some remote possibilities of deleting coil records and leaving dangling pointers behind. Each of these were remote possibilites but potentially possible non the less.

When the controller cleans up deleted coil records in the background, there was a small chance it could free a coil that some other part of the system — a screen dialog, or the host-computer/Eclipse browse position — was still pointing at, which can corrupt memory. The cleanup now waits if a pop-up dialog is open, refuses to delete the coil the host is currently looking at, and briefly locks the coil list the same way every other record type already does. This is extra insurance against a hard-to-reproduce field report about coils.