PrestoSoft Community

Well, nothing new or strange speaking about my memory, but I want to speak about my computer's memory...

I was working on my good old win2000 with a lot of heavy processes in background when EDP started complaining he was out of memory. Quite possible, even though I forgot to look at the task manager to be sure.
I clicked the message box "OK" button, but it kept reappearing. This too is quite normal.

What I wanted to do was to finish or stop some of the other processes, but I found no way to remove the "Out of memory" EDP dialog from my screen. It stayed firmly in the foreground before all the other windows. Very annoying.
As a workaround I put it in a corner (in punishment ) with just a little part of it in the screen.

After closing all the other processes, so I suppose there was then plenty of memory, I went back to it and clicked "ok" once again: as before it kept reappearing.

The story ended when, after I clicked "ok" once again, EDP crashed, so I finally got rid of the "Out of memory" dialog...

N.B. Beta 20 in operation.

In this exact moment I have my friend the "out of memory" dialog in the lower left corner of the screen (once again in punishment ) and the task manager in the lower right.

The task manager says:

• allocated memory
• Total: 299xxx
• Limit: 936256
• Peak: 736300

I now click the dialog "ok" button and... crash!

At least the dialog disappeared!

This is an odd problem. It sounds like your installation is corrupt. Could you post your options, or email them to us?

Good news: it seems that the latest beta (21) is immune.

Thank you.

Sorry, I spoke too early.

What caused the out of memory in beta 20 (comparing a couple of text files then copying a part of a file in the clipboard), in beta 21 doesn't, but I just got the same error while comparing two directories.
The task manager showed more or less the same use of memory as yesterday, with about 14 MB dedicated to EDP.

Each time I clicked "ok", EDP added/refreshed a line in one of the two panels.
When that panel was completely refreshed it started refreshing the other, and when even that was fully refreshed it restarted refreshing the first, then... I killed the process (no crashes).

I suspect it's my computer to blame, not EDP!
Sorry for the annoyance.

The only useful advice we got 'til now from this story is that EDP should use a better way to handle the out of memory condition.
I have to use the task manager to close the process!

Build 20 indeed could produce this type of behavior where you'd need to kill the process in such situations. However, other builds should not have required this.