View Single Post
Old 05-01-2021, 08:54 AM   #2
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,860
Karma: 6120478
Join Date: Nov 2009
Device: many
This could be a Qt 5.15.2 issue as I have never seen that happen for normal sized multi-file epubs. QtWebEngine uses its own render process that can die or be killed. On some platforms this can happen so much people actually track the render process dying and auto-restart it. But that has never been an issue for Sigil using Qt 5.12.

Things can also get out of sync and a signal lost and then Sigil appears to freeze waiting for that loadFinished signal. But simply closing that tab and reopening it frees Preview.

If the remainder of Sigil continues to work at normal speed it sounds as if the render process is getting killed somehow. We would need a list concrete steps you use to cause the freeze in order to track this down, We’re you just doing simple edits in CV or something else?
KevinH is offline   Reply With Quote