I know this is a real annoyance for everyone concerned - particularly when it’s so tricky to reproduce. I’m sorry.
As a mere user, though, I have a poor sense of where it figures on your list of priorities - particularly with so few apparently experiencing it.
Though I know you’ll appreciate that as a dedicated ‘fan’ of Dorico who uses it daily, to have this kind of ‘disability’ is pretty… ‘burdensome’ .
As a one-time developer myself I’m quite used to putting in tracer code that - although it produces masses of lines of output - can sometimes reveal the otherwise untroubleshootable.
I suppose what I’m really saying is that - since the one obvious approach of a member of your team wasting valuable hours waiting for it to manifest itself is impractical - I’d be happy to trial something else myself!
Am I remembering correctly that Dorico Pro 2 uses a new QT framework? Wouldn’t the fact that it hasn’t fixed the phenomenon suggest that it lies elsewhere?
Anyway, thanks for keeping it it!