I’m facing memory issues with Smack API version 3.0.4:
10% of my XMPPConnections (and related objects) aren’t
garbage-collected after disconnecting and setting the reference to null; not even by a forced collection.
done some extensive testing using a memory profiler, which shows that
all of my objects (which open and disconnect the XMPPConnection) are
propperly garbage-collected - it’s only org.jivesoftware objects
remaining in memory. I also made absolutely sure that
connection.disconnect() will be called on all connections before
According to the memory-profiler, the
XMPPConnection objects remaining in memory are still referenced from
PrivacyListManager, ServiceDiscoveryManager and MultiUserChat$1$1 (?)
It seems that the Java garbage collection (java version
1.5.0_09) is having problems with collection large sets of objects
containting circular references.
Maybe setting some of these references to null in XMPPConnection.disconnect() would help?
Thanks for any feedback!