Comment 7 for bug 1756695

Unfortunately this stack trace is client side, but we don't know what actually happened on the daemon during this situation to get to the bottom of the problem.

Can you reproduce this again? If so, it would be really useful if you could run the daemon under debug (or possibly valgrind) to figure out what that side was doing.