[KevinH]

I did some more searching for bugs related to Qt QSettings and found the following online:

From the 5.4.0 change log:

* [QTBUG-21739] The locking mechanism inside QSettings has changed
and is no longer compatible with the one of previous versions of
Qt. There might be corruption if two applications running different
versions of Qt are writing to the same config file at the same
time. You must also now have write permissions in the directory
containing the settings file in order to write settings.

So running multiple instances of Sigil with different versions of Qt could results in the behaviour some are reporting. It also may have nothing to do with it.

So we really need to rule this out and for every instance of Sigil running check the "About" box and report the build date and version, and Qt version, to make sure we are not mixing Qt versions across multiple instances of Sigil that are running.

It can be easy to run multiple different versions of Sigil at the same time given how programs are launched by menu and with changes in paths.

So if you can reproduce either of these QSettings related problems when running mutliple instances of Sigil on Windows, would you please check the "About" box and verify all versions of Sigil running are identical. That way we can rule this out as the cause.

Also as DiapDealer pointed out, this could also be related to virus checkers and other things interfering with reading of a shared file across processes.


KevinH