Memory Leak with MultiThread option
Bug #1054933 reported by
Ben
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gearman |
Incomplete
|
High
|
Brian Aker |
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.
summary: |
- Memory Link with MultiThread option + Memory Leak with MultiThread option |
Changed in gearmand: | |
assignee: | nobody → Brian Aker (brianaker) |
To post a comment you must log in.
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: /bugs.launchpad .net/bugs/ 1054933 /bugs.launchpad .net/gearmand/ +bug/1054933/ +subscriptions
>
> 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:/
>
> 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:/