Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.3
-
None
Description
I haven't seen any issues in normal usage, but while benchmarking `TinkerGraphComputer` with JMH, I noticed the forked JVM was hanging and had to be forcibly killed by JMH.
Thread[TinkerGraphComputer-boss,5,main] at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) <JMH had finished, but forked VM did not exit, are there stray running threads? Waiting 19 seconds more...>
The TinkerWorkerPool is being closed but not the ComputerService which causes the hang.