his.
>
>
> -Original Message-
>>> From: Daniel Etzold [mailto:detz...@gmail.com]
>>> Sent: Monday, November 23, 2009 4:17 AM
>>> To: users@qpid.apache.org
>>> Subject: Re: memory leak in qpid::client::Connection?
>>>
>>>
>>> H
Hi Carl,
I think memory pooling cannot be the problem since the requested memory
blocks should not differ much in size and therefore should be reused for a
new memory allocation request. Nevertheless, I modified the code a bit. Now,
it pauses for 30 seconds after 1000 iterations and prints the mem
fore leaks some associated memory.
I believe Andrew has some work in progress that should fix this.
-Original Message-
From: Daniel Etzold [mailto:detz...@gmail.com]
Sent: Monday, November 23, 2009 4:17 AM
To: users@qpid.apache.org
Subject: Re: memory leak in qpid::client::Connection?
Is it not just that the memory is not needed back yet from Linux? I.e.
gcc does not really try
to reuse memory until it needs to. If you run for say 30 seconds, then
stop the client for a few,
and then run it again. Or in the pause in-between start firefox... and
see if tc_mem_consolidate
is
niel Etzold [mailto:detz...@gmail.com]
> Sent: Monday, November 23, 2009 4:17 AM
> To: users@qpid.apache.org
> Subject: Re: memory leak in qpid::client::Connection?
>
>
> Hi Steve,
> I've created a jira report.
> https://issues.apache.org/jira/browse/QPID-2214
>
> Thanks,
Hi Steve,
I've created a jira report.
https://issues.apache.org/jira/browse/QPID-2214
Thanks,
Daniel
On Fri, Nov 20, 2009 at 4:23 PM, Steve Huston wrote:
> Hi Daniel,
>
> > when executing the code below (connecting and disconnecting to a
> local
> > broker without sending any messages) the mem
Hi Daniel,
> when executing the code below (connecting and disconnecting to a
local
> broker without sending any messages) the memory usage
> increases constantly
> and rapidly. After 10.000 iterations several hundred
> megabytes of resident memory are used.
Yikes.
> When commenting out the li
