I'm not sure how FPS is relevant at all in xhtml rendering. There is no video playing. So there are no "frames" involved at all.
I have no idea either, but worth mentioning, right? It's all data at the end of the day. FRAPS registers ~60 FPS with acceleration on, and 1–2 FPS without; and trust me: when
anything breaks down to the point where it hits 1 FPS, it tends to interrupt workflow
Also, after doing a little digging, it seems that Qt Web Engine does indeed leverage Open GL/Dirext X in its rendering pipeline, making FRAPS a very ample tool for diagnosing breakdowns in the rendering cycle.
Can you also confirm that you have no global Qt environment variables set on your system
It absolutely does solve the memory leak issues.
Can you also confirm that you have no global Qt environment variables set on your system
I have no idea what this would be, I never even heard of Qt until I came here to report the memory leak. So I suppose can assume, its a no?
And if you could provide the method with which you're able to accurately measure Sigil's Preview latency
I went simple, eyeballed it against "Lag Simulator Delux". The human brain is scarily accurate when it comes to detecting small fluctuations in Proprioceptive Feedback Delay, and one could probably expect a ±10% margin of error using this method, at least according to the current scientific consensus.
https://www.skytopia.com/stuff/lag.html