mirror of
https://github.com/pmmp/PocketMine-MP.git
synced 2025-06-18 17:34:11 +00:00
cf15a0913d
This required the following: - A generation task (taskA) to already be running for any chunk (chunkA) - A chunk (chunkB) is requested for generation, and the task (taskB) to do the generation is commenced immediately - chunkB generation promise is aborted (e.g. due to chunk unload) and taskB is orphaned - chunkB is subsequently re-requested, but ends up in the generation queue because taskB is still running - taskA completes and drains the generation queue - chunkB attempts to be populated a second time, but taskB has not yet been collected, resulting in an assertion failure. This bug has been appearing intermittently ever since PM 4.0 release. For most users there is no obvious effect since production servers don't have assertions enabled; however, it's unclear what kind of weird side effects this bug may have had.