From 6db588a19f970282bdbcba5c73a10d4866a63a11 Mon Sep 17 00:00:00 2001 From: dordsor21 Date: Tue, 5 Jan 2021 16:42:53 +0000 Subject: [PATCH] Don't allow FAWE to "deadlock" itself when post-processing history by switching to the primary ForkJoinPool - With enough chunks waiting to write to history, it's possible to fill the secondary fork pool up with locked threads, and thus prevent any threads from actually writing their history. --- .../com/boydti/fawe/object/changeset/AbstractChangeSet.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/worldedit-core/src/main/java/com/boydti/fawe/object/changeset/AbstractChangeSet.java b/worldedit-core/src/main/java/com/boydti/fawe/object/changeset/AbstractChangeSet.java index bf90ebc6a..7ee81bb94 100644 --- a/worldedit-core/src/main/java/com/boydti/fawe/object/changeset/AbstractChangeSet.java +++ b/worldedit-core/src/main/java/com/boydti/fawe/object/changeset/AbstractChangeSet.java @@ -351,7 +351,7 @@ public abstract class AbstractChangeSet implements ChangeSet, IBatchProcessor { wrappedTask.run(); return Futures.immediateCancelledFuture(); } else { - return Fawe.get().getQueueHandler().async(wrappedTask); + return Fawe.get().getQueueHandler().submit(wrappedTask); } } }