Gearman

Bug #1054933
Comment #1

Comment 1 for bug 1054933

Revision history for this message

Brian Aker (brianaker) wrote on 2012-09-23: Re: [Bug 1054933] [NEW] Memory Leak with MultiThread option

Do you have a test case that you can share?

Sent from my Ti85

On Sep 23, 2012, at 3:50, Ben <email address hidden> wrote:

> Public bug reported:
>
> 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.
>
> ** Affects: gearmand
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - Memory Link with MultiThread option
> + Memory Leak with MultiThread option
>
> --
> You received this bug notification because you are subscribed to
> Gearman.
> 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

Do you have a test case that you can share?

Sent from my Ti85

On Sep 23, 2012, at 3:50, Ben <Benny001.lim@gmail.com> wrote:

> Public bug reported:
>
> 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.
>
> ** Affects: gearmand
>     Importance: Undecided
>         Status: New
>
> ** Summary changed:
>
> - Memory Link with MultiThread option
> + Memory Leak with MultiThread option
>
> --
> You received this bug notification because you are subscribed to
> Gearman.
> 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