| 2018-12-07 07:10:26 |
Baker |
bug |
|
|
added bug |
| 2018-12-07 07:11:34 |
Baker |
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 classes defined in GearmanWorkerImpl.java line 228:
if (!functionList.isEmpty()) {
GearmanFunction fun = functionList.remove();
submitFunction(fun);
}
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() is done will mark it for GC.
I am using JDK 10, and version 0.6 of the client.
Please advise. |
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 classes defined in GearmanWorkerImpl.java 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() is done will mark it for GC.
I am using JDK 10, and version 0.6 of the client.
Please advise. |
|
| 2018-12-07 07:12:30 |
Baker |
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 classes defined in GearmanWorkerImpl.java 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() is done will mark it for GC.
I am using JDK 10, and version 0.6 of the client.
Please advise. |
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 classes defined in GearmanWorkerImpl.java 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. |
|
| 2018-12-07 07:14:27 |
Baker |
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 classes defined in GearmanWorkerImpl.java 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. |
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 GearmanWorkerImpl.java 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. |
|
