You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
InteractionModelEngine::mTimedHandlers had live objects on destruction, in a TestTimedHandler unit test.
(Replacing issue #11880Possible use of destroyed pool objects with specific issues for the few remaining instances.)
Proposed Solution
Someone with domain knowledge should decide where/whether remaining pool objects should be released (e.g. calling ReleaseAll() in the enclosing class's destructor), or whether some other action should be taken (e.g. extending the lifetime of the enclosing class instances).
The text was updated successfully, but these errors were encountered:
#### Problem
Fixesproject-chip#12504 ObjectPool leaks in InteractionModelEngine
#### Change overview
Call `ReleaseAll()` in `InteractionModelEngine::Shutdown()`;
since the comments there indicate that was the intent.
#### Testing
CI; no changes to external functionality.
#### Problem
Fixes#12504 ObjectPool leaks in InteractionModelEngine
#### Change overview
Call `ReleaseAll()` in `InteractionModelEngine::Shutdown()`;
since the comments there indicate that was the intent.
#### Testing
CI; no changes to external functionality.
Problem
InteractionModelEngine::mTimedHandlers
had live objects on destruction, in aTestTimedHandler
unit test.(Replacing issue #11880 Possible use of destroyed pool objects with specific issues for the few remaining instances.)
Proposed Solution
Someone with domain knowledge should decide where/whether remaining pool objects should be released (e.g. calling
ReleaseAll()
in the enclosing class's destructor), or whether some other action should be taken (e.g. extending the lifetime of the enclosing class instances).The text was updated successfully, but these errors were encountered: