Quote:
Originally Posted by Valloric
The Sigil core itself doesn't use any extra memory when you set a heading: it merely invokes a javascript command on the Book View QtWebkit instance to transform the element into a heading. What QtWebkit does in the background to accomplish this, I couldn't say. It's could be tracking changes for the internal undo stack. Again, I don't know for sure.
Some extra memory could be taken up by JavaScriptCore, but its garbage collector will take care of any unused memory when it becomes unused.
Bottom line, don't worry about it. But I'll take a closer look just in case.
|
That was all I was asking.
It just seemed pretty high overhead. 57M when book first loaded to 2+ times. Things were starting to slow down, so I loaded process explorer and left it showing on one of my monitors while I did thing in Sigil.
I saw the CV editor jump on some pages, but not others. Every time it happened there appeared a line with "CDATA" in it. Not all pages visited in CV get this line
