View Single Post
Old 03-05-2019, 03:07 PM   #142
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,893
Karma: 6120478
Join Date: Nov 2009
Device: many
One way to test this, (if you know how) is to add a utf-8 byte order mark to your sigil.ini file with an editor (with Sigil shutdown) and then start and run Sigil for some time to see if problems develop again or not.

This is very strange. We may have to revert back to non utf-8 ini file format and make a new release.

Let's wait to hear from DiapDealer on what he thinks.

KevinH


Quote:
Originally Posted by KevinH View Post
Your sigil ini file does not even have a preserve entities section! In addition your searches ini file shows minor corruption.

Not sure why this leads to an memory bloat and slowdowns but according to the following Qt Bug report:

https://bugreports.qt.io/browse/QTBUG-40796

and this report:

https://bugreports.qt.io/browse/QTBUG-54510

this may have to do with something inside Qt related to QSettings eating memory but only when the ini files are set to use utf-8 encodings.

Thanks!

KevinH
KevinH is online now   Reply With Quote