exactly the same here : this error wasn't an issue in 10.5, but it might be the cause of our KP on 10.6 ...

I don't know how much it can help more talented people to (hopefully) solve the problem, but I'll mention the observed link on netkas' blog ...