i think that’s the problem.
you surely know that this means that the following code is on another thread.
the print then creates a race condition with the output device (the console)
it’s mostly a guess, but seems reasonable since the error comes from the outputdevice.
i can’t remember if you can or can’t use logs on bg threads, since i never did, but makes sense it’s not threadsafe.
i would expect though some kind of flag to make it threadsafe.
though it’s pretty weird that condition is hit, since you specify the asynctask to run on game thread. which “should never happen” 
.