Also glibc malloc does not seem to have the problem.Ī breakthrough. jemalloc 4.5 does not seem to cause the problem. So far we've worked around this by not upgrading to jemalloc 5.1.
The application exits the loop early because of a timeout caused by the deadlock. The application should finish all iterations and not exit the loop early. STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : The thread that the monitor references is parked in a threadpool waiting for its next task.Įxample log output when a deadlock occurred.
We've run into an issue where our application deadlocks, and when looking at thread dumps we see that threads are waiting for an object monitor that no other thread is currently holding. We've tested on the following operating systems: Debian 8 and 9, and Ubuntu 16.04.Īnd these OpenJDK JVM runtimes: multiple versions of 1.8 between 1.8.0.121 and 1.8.0.202, 1.9, and 1.11.
0 kommentar(er)
