This resolves the problem created by #412, without reverting the change that created a memory error.
Essentially the problem is the queue is shut down without being removed from the peer manager, which continues to send it messages, that have no effect. This change adds a hook so that the queue itself can notify the peer manager it's been shutdown.
Goals
This resolves the problem created by #412, without reverting the change that created a memory error.
Essentially the problem is the queue is shut down without being removed from the peer manager, which continues to send it messages, that have no effect. This change adds a hook so that the queue itself can notify the peer manager it's been shutdown.