Have you tried the release version of 116? I’ve never seen that assert before but it’s possible that a debug statement is getting tripped up and there is a bug in the debug statement itself.
If you can reproduce it, can you run with debugview and get the trace from that? That might give me an idea where in the code it is tripping up.