MobileRead Forums - View Single Post

DiapDealer · 10-01-2024, 06:49 AM

It's always possible. A successful Windows QtWebEngine compilation nearly always has warnings of potential memory leaks. But the Qt used with Sigil 2.3.1 is the same one used with Sigil 2.3.0, so I would expect identical results. Any info on just how long Sigil had to stay running to get to the numbers you screen capped?

For the record... Sigil almost never needs very much GPU for rendering epubs. That's why we added the ability to turn off WebEngine's hardware acceleration in Sigil's preferences: to handle the edge cases where WebEngine doesn't always play nice with certain video cards. Have you tried disabling that?

10-01-2024, 06:49 AM	#2
DiapDealer Grand Sorcerer Posts: 28,645 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It's always possible. A successful Windows QtWebEngine compilation nearly always has warnings of potential memory leaks. But the Qt used with Sigil 2.3.1 is the same one used with Sigil 2.3.0, so I would expect identical results. Any info on just how long Sigil had to stay running to get to the numbers you screen capped? For the record... Sigil almost never needs very much GPU for rendering epubs. That's why we added the ability to turn off WebEngine's hardware acceleration in Sigil's preferences: to handle the edge cases where WebEngine doesn't always play nice with certain video cards. Have you tried disabling that? Last edited by DiapDealer; 10-01-2024 at 09:27 AM.