My guess, from 3.4 Patch notes:
We don’t have much details about what they did, but I guess that devs added multi-threaded tasks to fix the quoted bug.
Because it really looks like several process are competing to act first and sometimes, one goes before the others which should not happen (i.e. the bug). A casual asynchronous issue. Good luck to fix it and test it correctly.