Hey guys, I think we might be onto something with https://w-g.pw/l/ZO5Z ...
I'm going to cut a new release in the next few hours here. When that's released, would you try updating to 0.4.10, going back to using the kernel implementation, and letting me know whether the problem resurfaces? In the absence of being able to locally produce this on a debuggable machine, I think this kind of trial and error is all we've got. Hopefully the theory behind https://w-g.pw/l/ZO5Z is correct. Jason
