Please bear with us… this issue is not easy to reproduce (we have never been able to do it in any test environment… if we had been able to, we certainly would never have released it).
That said, based on the log file, I think I might have an idea of what sometimes causes this… I put some protection around this area to try and stabilize it (this change can be found in 2.3.11). No guarantees, but I have high hopes that this issue will disappear…
Please let us know.
Ken