|
The point that seems to be missed in this discussion is that Preview ALWAYS loads the entire file each time. It does this everytime a change is made in code in the CodeViewEditor. It always has.
The clearing of the memory caches is only done if you ask to Preview a file that is from a different CodeViewEditor Tab/Resource. If you look at the code it checks the url against the currently loaded one to determine if it is okay to clear memory caches that hold fonts, javascripts, images and other resources. The current cache is worthless in that case anyway.
In addition, unlike a browser, all files are local and there is no network delay to load them. So most file io uses ram buffers anyway, so that the page cache is redundant in these cases.
So clearing of memory caches when they are not needed for the page you are about to load will help free up memory.
It does in fact help keep the memory footprint from constantly growing which is the issue we are trying to solve.
So please as DiapDealer said, let us separate annoyance from screen flashing to load a new position in Preview from a system slowdown that cause the wait cursor to appear and the system to become unusable until Sigil and the computer is restarted.
Also Becky, what Windows 10 update and exact build are you using? Are you seeing Sigil's memory use growing to over 1 gig from just an hour or so from working with it?
|