That’s right, I can see that the unexpected edges has a higher priority over the speed of execution.
It’s just that for my use case it would be wonderful if there was no delay because the rest of the operations using three.js are snappy. (I am creating a commercial configurator).
Edit: But as I said in my previous post: the delay is gone after fixing the warning/error. So I’m very happy with your advice!