Memory Leak with MultiThread option

Bug #1054933 reported by Ben on 2012-09-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman
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.

Ben (benny001-lim) on 2012-09-23
summary: - Memory Link with MultiThread option
+ 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

Ben (benny001-lim) wrote :

Hi Brian,

I can reproduce with a very simple test case.

1/ Start: gearmand -t 4
2/ In the directory "Sample" of the gearman distribution: I can find 2 binaries "reverse_worker" and "reverse_client_bg"
3/ I start reverse_worker
4/ Write a shell script Test.sh
content of the shell script :1000 time the same command:
reverse_client_bg aaabbbccc
reverse_client_bg aaabbbccc
reverse_client_bg aaabbbccc
....
reverse_client_bg aaabbbccc

5/ Start he Test.sh

Keep it running and after a while I can see the gearmand process memory increasing 4K by 4K.

Let me know if I can help.

Rgds

Hi,

Is the work being processed?

Cheers,
 -Brian

On Sep 23, 2012, at 12:19 PM, Ben <email address hidden> wrote:

> Hi Brian,
>
> I can reproduce with a very simple test case.
>
> 1/ Start: gearmand -t 4
> 2/ In the directory "Sample" of the gearman distribution: I can find 2 binaries "reverse_worker" and "reverse_client_bg"
> 3/ I start reverse_worker
> 4/ Write a shell script Test.sh
> content of the shell script :1000 time the same command:
> reverse_client_bg aaabbbccc
> reverse_client_bg aaabbbccc
> reverse_client_bg aaabbbccc
> ....
> reverse_client_bg aaabbbccc
>
> 5/ Start he Test.sh
>
> Keep it running and after a while I can see the gearmand process memory
> increasing 4K by 4K.
>
> Let me know if I can help.
>
> Rgds
>
> --
> 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

Brian Aker (brianaker) on 2012-09-28
Changed in gearmand:
assignee: nobody → Brian Aker (brianaker)
Ben (benny001-lim) wrote :

Hi Brian,

Yes, the work is being processed.
In addition, using the "Admin interface" and status command, I can see no No more jobs in the queue.

Take care
-Ben

Brian Aker (brianaker) wrote :

Hi,

Are you sure that memory is leaking, or is the process just growing as it fills out queues?

Cheers,
    -Brian

Ben (benny001-lim) wrote :

Hi,

Yes, I am sure that the memory is Leaking.

Also same test with option "-t 1" does not leak.

I have made a long run test, and the process keeps growing for ever.

Thxs
-Ben

Thanks, let me try to see if I can find it.

Right now valgrind is not showing any sort of leak.

Cheers,
 -Brian

On Oct 6, 2012, at 10:21 PM, Ben <email address hidden> wrote:

> Hi,
>
> Yes, I am sure that the memory is Leaking.
>
> Also same test with option "-t 1" does not leak.
>
> I have made a long run test, and the process keeps growing for ever.
>
> Thxs
> -Ben
>
> --
> 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

Ben (benny001-lim) wrote :

Hi Brian,

Any news on this memory leak issue. I am stuck.

Thxs a lot.
Bye
-Ben

Ben (benny001-lim) wrote :

Hi,

Any news on this? I still face the issue.

Rgds

Brian Aker (brianaker) wrote :

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

Clint Byrum (clint-fewbar) wrote :

No additional reports in 2 years, I think this may be platform specific.Ben, if you're still around and still have the affected system I'd love to get my hands on your test code and the platform details so we can try to reproduce.

Changed in gearmand:
status: New → Incomplete
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions