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
If running remove() on the Registration returned by ComponentConnectionContext::setActivationHandler while there is some attached component, then all detach handlers will be removed but we won't be running deactivateConnection() which takes care of removing references to the ComponentConnectionContext instance from the global handler lists in BeaconHandler and ServiceDestroyDelegate. Unless I've read the code wrong, this means that we would end up leaking some memory.
The text was updated successfully, but these errors were encountered:
If running
remove()
on theRegistration
returned byComponentConnectionContext::setActivationHandler
while there is some attached component, then all detach handlers will be removed but we won't be runningdeactivateConnection()
which takes care of removing references to theComponentConnectionContext
instance from the global handler lists inBeaconHandler
andServiceDestroyDelegate
. Unless I've read the code wrong, this means that we would end up leaking some memory.The text was updated successfully, but these errors were encountered: