MobileRead Forums - View Single Post

KevinH · 06-07-2019, 10:01 AM

You may have to change your thinking a bit for Windows 10. If the AI (which is not smart) in Windows 10 defence does not like something a program is doing for any reason it will start to increase scans of generated files, slowing it down and greatly hurt performance. Something as simple as compiling a python py file, or creating a bunch of files in the temp folder can trigger it. So unless you whitelist these specific folders, nothing will help.

In addition other Windows security like CFG has been documented to leak memory and will improperly slow down any program that uses JIT compiled javascript with garbage collection scanning threads that do not start at repeated process memory locations. This is exactly what QtWebKit and QtWebEngine does!

See the thread about what Google engineers found for serious bugs in Windows 10 and earlier, that I posted in the original Release thread.

These are things we can not work around as they are driven by design choices in Qt. Disabling CFG for Sigil and whitelisting it against anti-virus (it is not a web browser) may be the only way around this till Windows wakes up.

If you are truly worried about security, you may want to generate a separate non-admin account to isolate Sigil and your other ebook creation activities from other programs where you can use different security settings more safely.

06-07-2019, 10:01 AM	#8
KevinH Sigil Developer Posts: 8,884 Karma: 6120478 Join Date: Nov 2009 Device: many	You may have to change your thinking a bit for Windows 10. If the AI (which is not smart) in Windows 10 defence does not like something a program is doing for any reason it will start to increase scans of generated files, slowing it down and greatly hurt performance. Something as simple as compiling a python py file, or creating a bunch of files in the temp folder can trigger it. So unless you whitelist these specific folders, nothing will help. In addition other Windows security like CFG has been documented to leak memory and will improperly slow down any program that uses JIT compiled javascript with garbage collection scanning threads that do not start at repeated process memory locations. This is exactly what QtWebKit and QtWebEngine does! See the thread about what Google engineers found for serious bugs in Windows 10 and earlier, that I posted in the original Release thread. These are things we can not work around as they are driven by design choices in Qt. Disabling CFG for Sigil and whitelisting it against anti-virus (it is not a web browser) may be the only way around this till Windows wakes up. If you are truly worried about security, you may want to generate a separate non-admin account to isolate Sigil and your other ebook creation activities from other programs where you can use different security settings more safely. Last edited by KevinH; 06-07-2019 at 03:57 PM.