https://bugs.kde.org/show_bug.cgi?id=524780
--- Comment #5 from Ralf Habacker <[email protected]> --- 50 seconds seems surprisingly high compared to what I can reproduce on another system. I did an additional check on another host (13th Gen Intel® Core™ i5-13600KF, PCIe M.2 SSD) using the same ~1.6 MB HTML document: ../kmymoney-build/bin/test-qtextbrowser HTML size: 1603650 bytes setHtml: 2800 ms show: 5253 ms processEvents: 4 ms documentSize: QSizeF(87061, 2462) time: 0 ms ../kmymoney-build/bin/test-alkwebpage (QWebEngine) HTML size: 1603650 bytes load: 2 ms show: 21 ms processEvents: 37 ms So on this system the complete QTextBrowser path takes roughly 8 seconds, while the QWebEngine version takes only a few tens of milliseconds. This makes me wonder whether the reported ~50 seconds include some additional processing outside the actual HTML parsing/rendering, or whether there is a significant system-dependent factor involved. In particular, processEvents() only takes 4 ms after show(), so the delay does not seem to be caused by a large backlog of pending events. -- You are receiving this mail because: You are watching all bug changes.
