And please ... try to separate high memory usage, from sluggishness. In fact for the purposes of providing steps to reproduce, do me a favor and stop looking at or reporting memory usage. It's not at all helpful. Sigil on Windows can use a crap-ton of memory and still be completely responsive.
I can't get Sigil 0.9.13 to bog down on any of my Windows 10 machines--physical or virtual. The only time I had horrific performance issues on Windows 10 is when I somehow managed to accidentally assign Windows compatibility settings to Sigil.exe.
It's all really kind of moot anyway, because the next release of Sigil (with webkit) has had extensive work done to reduce the memory footprint. We've had some good reports from beta testers (who were experiencing severe performance issues) that while maybe not completely eliminated, the sluggishness they were experiencing was greatly reduced. And after that, we switch to webengine instead of webkit. Early testing there indicates no performance issues.
|