You can run a simple connection create/close loop and check the number of times MINANetworkDriver.sessionClosed gets called.
When I did that I observed this particular method got only called 49 time when I ran the loop for 50 iterations, 99 times for 100 and 994 for 1000. Am I missing something here?. I also see that the ProtocolEngine_0_10 instance count in heap is equal to the number of times this method did not get called. Hence the memory leak. These objects retain in the memory as they are not removed from the _typeMap in ConfigStore as removeConfiguredObject does not get called. Thanks, Danushka On Tue, Mar 22, 2011 at 5:09 AM, Danushka Menikkumbura < [email protected]> wrote: > Hi devs, > > I see sometimes (1/50) MINANetworkDriver.sessionClosed does not get called > causing a memory leak. Is this a known issue?. > > Thanks, > Danushka >
