Shut down InteractionModelEngine during DeviceController shutdown. #7629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Otherwise if we have an IM action in flight at shutdown time we will
effectively leak the object managing it, and after a few
shutdown/restart cycles for the stack not be able to send any more IM
actions.
Problem
If I shut down and restart DeviceController a few times, and the shutdowns happen to come while there is a CommandSender outstanding (in that we sent a command and a response has not come back), then eventually we run out of CommandSenders.
Change overview
Make sure to shut down CommandSenders when we shut down DeviceController.
Testing
Manual testing with a bug added to chip-all-clusters-app that causes it to shut down the DeviceController while CommandSenders are life. Will try to add some automated tests too.