Classloading instigates OutOfMemoryError

Bug #1807338 reported by Baker on 2018-12-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman Java

Bug Description

Not sure if this project is being maintained, but thought I'd try in any case.
There appears to be a bug with the worker not releasing objects defined in line 228:

226 if (!functionList.isEmpty()) {
227     GearmanFunction fun = functionList.remove();
228     submitFunction(fun);
229 }

What ends up happening is new classes are constantly being instantiated but not being released, and thus the GC isn't cleaning them up. If a MaxMetaspaceSize is set, it'll instigate a OOM exception. If on the other hand, no MaxMetaspaceSize is set, it will deplete all the ram given enough time.

I suspect (yet to try) that setting "fun = null;" after submitFunction() will mark it for GC.

I am using JDK 10, and version 0.6 of the client.

Please advise.

Baker (bakerman11) on 2018-12-07
description: updated
description: updated
description: updated
palik (1-infe-w) wrote :

> Not sure if this project is being maintained

It doesn't look so.

Last release:
97. By Eric Lambert <email address hidden> on 2014-09-09

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers