View Single Post
Old 04-04-2019, 10:37 AM   #106
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,809
Karma: 6000000
Join Date: Nov 2009
Device: many
One interesting test just before you go to bed at night would be to:

1. close the Preview window and exit from Sigil (to prevent the Preview Window from reopening)
2. restart Windows 10
3. start a fresh copy of Sigil and open the latest version of our User's Guide (so we are all starting with exactly the same epub). Verify that Preview is NOT open.
4. Then check and write down the memory usage of Sigil
5. Then close the lid to sleep for the night

Once you get up the next day.

6. Reopen the lid and **without** clicking on Sigil (which would start new gui threads) check the memory and write it down.

Let us know what if anything changed during sleep.

Then repeat the entire process the next night but with Preview ***Open***.

That way we can see how much memory consumptions changes overnight with and without Preview being open.

This may help isolate any increased memory usage to the Qt Webkit or not.

Thanks!

KevinH
KevinH is offline   Reply With Quote