Since 0.9, specifically commit ab7184ef (fixing segfaults happening when the low level library destructor was running earlier than epicsExit), shutdown is left to the low level client, which does not cancel the subscription before shutting down the connection.
This complies with the protocol specification, but leaves behind server-side resources (e.g. subscriptions), which the server might only be cleaning up after a configurable time (default: 20 min).
On regular exit, the IOC should try to properly and completely shut down the existing sessions.
Since 0.9, specifically commit ab7184ef (fixing segfaults happening when the low level library destructor was running earlier than epicsExit), shutdown is left to the low level client, which does not cancel the subscription before shutting down the connection. This complies with the protocol specification, but leaves behind server-side resources (e.g. subscriptions), which the server might only be cleaning up after a configurable time (default: 20 min).
On regular exit, the IOC should try to properly and completely shut down the existing sessions.