Comment 10 for bug 1054933

Hi,

No one else has reported it. Memory will grow as more clients/workers are brought in.

Cheers,
 -Brian

On Jan 9, 2013, at 7:57 AM, Ben <email address hidden> wrote:

> Hi,
>
> Any news on this? I still face the issue.
>
> Rgds
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1054933
>
> Title:
> Memory Leak with MultiThread option
>
> Status in Gearman Server and Client Libraries:
> New
>
> Bug description:
> Hi,
>
> I was running Gearmand 0.14 till now. With the number of connected workers and Clients, I required to use the Threading option. (Option -t).
> Whatever if the number of Thread Started, I am facing to a Memory Leak in Gearmand process.
> It increases 4K by 4K....
>
> Also, I downloaded version 0.24, and I am still facing The same Memory
> Leak.
>
> Please Allow me to create a bug report, as I did additional testing on this one.
> You can simply use the Reverse_clientbg and reverse_worker delivered in the Sample package distribution.
>
> For information I am using LibEvent 1.4.14b-Stable distribution.
>
> Is it confirmed to be a bug?
>
> Best Regards
> -Ben.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gearmand/+bug/1054933/+subscriptions