Just run the sample client that I have mentioned in [1] and see the number of ProtocolEngine_0_10 and related objects in heap on JProfiler. You should be able to see 50 of them.
[1] - https://issues.apache.org/jira/browse/QPID-3162 Thanks, Danushka On Thu, Mar 24, 2011 at 12:13 AM, Danushka Menikkumbura < [email protected]> wrote: > Hi Andrew, > > I just checked the latest trunk. The issue is still there, the memory > consumption is very less, though. As I can see its because of the way the > incomplete Method array is allocated in Assembler now. But still I can see > the same result w.r.t. instances that are not GC'ed. > > Thanks, > Danushka > > > On Wed, Mar 23, 2011 at 6:07 PM, Andrew Kennedy < > [email protected]> wrote: > >> Also, >> >> I will add a test case to the new network code. I haven't seen this >> behaviour on the branch I'm working on, so it may be fixed. I'll wait for >> your patch before checking again, though. >> >> I should have more time to work on the in-vm networking branch now that >> I've started a new job; I know I said it would be part of 0.10 but >> circumstances meant I didn't have enough time to finish the work. >> >> Andrew. >> -- >> -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ; >> -- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ; >> >> >> On 23 Mar 2011, at 10:47, Andrew Kennedy wrote: >> >> Hi, Danushka. >>> >>> I'll take a look at this, it looks like a race during session close, >>> which we have seen before. >>> >>> Andrew. >>> -- >>> -- andrew d kennedy ? edinburgh : +44 7582 293 255 >>> >>> >>> >>> >>> On 23 March 2011 00:43, Danushka Menikkumbura >>> <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Any idea what is going wrong here?. >>>> >>>> Thanks, >>>> Danushka >>>> >>>> On Tue, Mar 22, 2011 at 12:30 PM, Danushka Menikkumbura < >>>> [email protected]> wrote: >>>> >>>> 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 >>>>>> >>>>>> >>>>> >>>>> >>>> >> >
