[Tex2002ans]

Originally Posted by BetterRed

Or, maybe the "Samsung optimized mode" tweaks the video driver, IIRC there were/are video driver issues in some versions of Qt.

Hmmmm...

Originally Posted by Ashjuk

As Tex2002ans said it mostly relates to how the computer goes sleep after a set time of inaction, and what happens when you press various buttons.

Well, the default Windows 10 power settings pretty much do that.

But the more serious tweak "Power Saver" does is downclocking/throttling more aggressively (especially when on battery).

I was doing a few searches to try to figure out what "Samsung Optimized Power" mode does:

http://forum.notebookreview.com/thre...lanced.752592/

The 'Samsung Optimised' power plan seems to cap the CPU cores to 50% of their regular full clock speed on my NP700Z7C. [...]

There's also these:

"What causes Windows to freeze for no apparent reason?"

NotebookReview Forum: "Anyone here have the NP550P7C 17"?"

where users were also having trouble with Samsung's power mode.

Now... why it hapens on Sigil 1.5.1 and not 1.4.3... unsure. But I'm still suspecting it has to do with with Samsung's throttling.

Question to repilo: Is this happening while on battery? Or is it happening when plugged in too?

And did that "Balanced" power mode solve the freezing issue now for Sigil 1.5.1?

Does this happen in anything else on your computer? For example, watching a high resolution video on Youtube? Or opening up a very large document in Word/LibreOffice?

Originally Posted by DiapDealer

Closing the Preview window under those conditions also eliminates the constant refreshing/reloading going on with every individual Code View edit.

Calibre's Preview doesn't choke as much as Sigil's.

If I remember correctly, if you open super large HTML file:

• Calibre lets you use Code View at full-speed while Preview is chugging away—displaying a temporary "Loading preview, please wait...".
• Sigil's freezes/stutters the entire program if Preview is opened.

Note: Although I haven't really messed with large single files in a while...

But when I do, I always do my cleanup/splitting in Calibre first.

Once it's in bite-sized chunks, then I vastly prefer Sigil.

Originally Posted by KevinH

Whoever recommends people to use one large xhtml file is really off the mark and does not understand anything about how technology or browsers really work.

Again, the monolithic HTML file is usually a temporary initial step.

For example, merging together a Gutenberg mess or importing a Word "Save As HTML".

You initially have your huge file, then do your splitting.

But if that initial import is brutal, and Sigil is stuttering/freezing up... it makes it frustrating even if you knew what a subset of the underlying problem was (View > Preview (F10)).

* * *

Artificial Test Case

Take any reasonably large EPUB (>1MB), merge into a single HTML file, then poke away at Code View/Preview.

Here's a great example of a 3.9 MB EPUB (~1.4 million words):

"The Complete Libertarian Forum"

I just tested Sigil 1.5.1 in my VM:

1. Merged all chapters in the EPUB into "Chapter1.html".

2. Clicking View (or anywhere else) instantly froze up Sigil for a while.

3. Once the menu finally opened, even moving the mouse or hovering over menu items caused a huge delay + Sigil (Not Responding). Clicking or doing anything froze it up for another many seconds.

Calibre's Editor handles that type of "monolithic mess" at full-speed.

* * *

Side Note: I also believe this happens when:

• Copying/pasting in huge amounts of material.
• Merging lots of files together + updating all the links

Where Calibre copies/pastes in a second (may have to do with syntax highlighting + previewing in a separate thread?)... Sigil completely chugs.

I also think that EPUB's a brutal case to test merging lots of files together + updating all the internal links.

Here were my rough timings:

Calibre: ~2 seconds to merge all files. Instantly able to edit.

Sigil: ~60 seconds to merge all files. ~45 more seconds until Code View was even scrollable/clickable. (Preview was closed. Didn't retest with Preview open.)