After almost 24 hours, I have managed to solve this issue as painless as possible.

The best way is to actually remove almost all printers and reinstall them.

The only printers that I did not remove were 'One Note' and 'Send to One Note'.

Everything else including the printers from 'optionalfeatures.exe' had to be removed and reinstalled after a reboot.

Now e-sword is OK, with COMMITTED never above 9GB.

Very strange problem considering that printing has nothing to do with e-sword which does not even have a print function!

Well, I hope it does not return.

Thanks to Bug Hunter for your help in replicating this.

btw, no need for copy paste.

To replicate you can 

1. select text in a bible

2. choose parallel (loaded with 3 or more bibles)

3. resize the window repeatedly.

Also when the print spooler service is disabled then problem goes away. I have no idea why!

Thanks for checking.

I created a new profile and it does not happen there either.

Thanks again.

Live demo.

I stopped short of the 73.8GB mark for obvious reasons of the video capture failing.

My Windows does not suffer from memory problems.

It has 24GB RAM, but RAM is not the problem.

As I stated before the problem is COMMIT memory.

Maximum Commit is specified as pagefile size (if exists) + memory size (23.8GB)

Therefore esword adds huge chunks to this until the maximum size of 73.8GB is reached (50 + 23.8).

Although pagefile size is automatically managed by windows at 73.8 we reach MAX COMMIT

The issue here is why esword needs so much memory committed, just for selecting text, or changing to parallel? 

Why not release it afterwards? 

my oversight. I added the windows version. 

BTW, my windows has no mods or tweaks.

To replicate on Windows 10 Home 64 bit:

1. Open task manager > Performance > Memory and watch the COMMITTED number.

    Or Get process explorer which can show you the 'system commit'. Open the relevant memory panel and keep it in view.

2. Open esword and with the mouse, select a big portion of text from any bible text. This will add 1GB of memory to 'system commit'.

3. Alternatively you can just go to 'parallel bibles' which will add 5GB to the 'system commit', every time!

4. Not much later, you will start getting a black screen, screen interruptions, and eventually an event 2004 ('Microsoft-Windows-Resource-Exhaustion-Detector')

I hope this helps.

Additionally,

I noticed that the problem is not entirely continuous. 

i.e. While Viber is running, you may get some short durations of time, or some chapters in Daniel which may end up getting captured. In the next second, the error may come up again. So bear this in mind.

The program causing this issue with CTRL+C is "VIBER desktop". 

When I close this program by right click and exit, then eSword functions properly.

Can someone please take a look and see if they can replicate this?

Keep in mind that all other applications can access the clipboard while Viber is on.

This leads me to conclude that the problem lies with e-sword.