5b6dd8e3f7
The lambda we schedule in 25ms captures a strong reference to the XMPPConnection. However the lambda is part of the scheduled action, which we save in the renewEntityCapsScheduledAction field. This causes a memory leak, since the ServiceDiscoveryManager now holds a strong reference to its XMPPConnection. Fix this by obtaining the strong reference to the XMPPConnection, if one still exists, within the lambda. Fixes SMACK-926. Reported-by: Damian Minkov <damencho@jitsi.org> |
||
---|---|---|
.. | ||
packet | ||
provider | ||
AbstractNodeInformationProvider.java | ||
DiscoInfoLookupShortcutMechanism.java | ||
EntityCapabilitiesChangedListener.java | ||
Feature.java | ||
NodeInformationProvider.java | ||
ServiceDiscoveryManager.java | ||
package-info.java |