Submitting attached jobs causes GearmanClientImpl to leak memory

Bug #400466 reported by Eric Lambert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman Java
Fix Released
Medium
Eric Lambert

Bug Description

Submitting attached jobs causes GearmanClientImpl to leak memory.

The root cause of this problem is that for an attached (as in non-background) job, the Gearman Server will send back events to the client (such as JOB_CREATED, WORK_COMPLETE, etc). Currently, when the client receives such an event, it handles it and then places the event in the updatedEvents collection so that they can be returned to the user when the use calls selectUpdatedEvents(). If the selectUpdatedEvents() method is never called, than the elements of the updatedEvents collection are never removed, and 'viola' memory 'leaks'

For the time being this can work-around by calling selectUpdatedEvents() on a semi-regular basis.

Related branches

Revision history for this message
Eric Lambert (elambert) wrote :

mark as medium because an easy workaround exists

Changed in gearman-java:
importance: Undecided → Medium
milestone: none → 0.02
Eric Lambert (elambert)
Changed in gearman-java:
assignee: nobody → Eric Lambert (elambert)
Eric Lambert (elambert)
Changed in gearman-java:
status: New → Fix Committed
Eric Lambert (elambert)
Changed in gearman-java:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.