Jump to content

Please read the Forum Rules before posting.

Photo
- - - - -

BUG - Serious Memory Leak leads to Resource Exhaustion


15 replies to this topic

#1 ajoannou

ajoannou

    New to Bible Support

  • Members
  • Pip
  • 10 posts
Offline

Posted 05 June 2020 - 04:54 AM

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.


Edited by ajoannou, 05 June 2020 - 05:40 AM.


#2 Katoog

Katoog

    e-Sword Fanatic

  • Members (T)
  • PipPipPipPipPip
  • 1,006 posts
Offline

Posted 05 June 2020 - 05:08 AM

e-Sword 12 is a 32 bit program so the maximum RAM memory is 4 GB.

If you have memory trouble then use lest resources and don't load a big dictionary like the one of Webster except if you deselect other Resources.

You can select the resources that you load: by Options and Resource Settings.

 


Restored Holy Bible 10 and the Restored Textus Receptus

http://rhb.altervista.org/homepage.htm


#3 Katoog

Katoog

    e-Sword Fanatic

  • Members (T)
  • PipPipPipPipPip
  • 1,006 posts
Offline

Posted 05 June 2020 - 05:15 AM

I wonder how you even can add "5GB" to a 32 bit program without tweaking the memory-management of your Windows edition.

And you did not mention which edition of Windows that you use.

 


Restored Holy Bible 10 and the Restored Textus Receptus

http://rhb.altervista.org/homepage.htm


#4 ajoannou

ajoannou

    New to Bible Support

  • Members
  • Pip
  • 10 posts
Offline

Posted 05 June 2020 - 05:39 AM

my oversight. I added the windows version. 

BTW, my windows has no mods or tweaks.



#5 ajoannou

ajoannou

    New to Bible Support

  • Members
  • Pip
  • 10 posts
Offline

Posted 05 June 2020 - 05:47 AM

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? 



#6 JPG

JPG

    Bug Hunter

  • Moderators
  • 1,064 posts
Offline

Posted 05 June 2020 - 05:53 AM

Could you make a video of this happening, post here.?



#7 ajoannou

ajoannou

    New to Bible Support

  • Members
  • Pip
  • 10 posts
Offline

Posted 05 June 2020 - 06:11 AM

Live demo.

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

Attached Files


Edited by ajoannou, 05 June 2020 - 06:20 AM.


#8 JPG

JPG

    Bug Hunter

  • Moderators
  • 1,064 posts
Offline

Posted 05 June 2020 - 06:26 AM

I replicated your actions and I did not get the rise in Committed. Hope you get your problem sorted.



#9 ajoannou

ajoannou

    New to Bible Support

  • Members
  • Pip
  • 10 posts
Offline

Posted 05 June 2020 - 06:57 AM

Thanks for checking.

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

Thanks again.



#10 JPG

JPG

    Bug Hunter

  • Moderators
  • 1,064 posts
Offline

Posted 05 June 2020 - 06:58 AM

Great news.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Similar Topics



Latest Blogs