Given the bugs that Google found in Windows 10, I strongly recommend disabling CFG only for Sigil as unlike an actual web browser, Sigil is not visiting possible mallicious websites over the internt and really does not need that type of protection on a non-server machine. At least until Microsoft actually plugs their memory leak in CFG.
My 2 cents.
Kevin
Quote:
Originally Posted by Turtle91
I'm fully updated on 1809. I tried disabling the CFG but it was still getting up to 1.4Gb before I finished my edits. It did seem like the memory usage wasn't affecting Sigil as much though... I didn't notice as drastic a slowdown???
|