At first thank you very much for your spended time.
Just in case there's a total missunderstanding between us, I've recorded a screen-capture (only 2MB!) of my understanding of the "Memory Leak" of SED:

Please have a look at the following video:

SED-Memory-Video

the video is taken with the latest Lite-C SED, so anyone is able to test it, but the behaviour is the same with the latest official version.
You clearly see the memory increasing in the demo (as well in the Task-Manager as in ProcExp) ~10 MB per run.

BTW: to speed things up i can also interupt the engine WHILE loading/compiling (pressing the red stop button) resulting in the same memory-leak. ==> With this method i'm able to let SED reserve + 1GB in less than 2 minutes.

Yep, debug mode eats too many memory... And its binded to F5 key, if i'm right

... and Ctrl+F5 calls Test Mode and there is no memory leaks anymore!
In the menu they are changed:


Just bind Test Run to F5 and Debug Run to Ctrl+F5

just in case the video is too big for your monitor, a smaller version without ProcExp

SED-Memory-Video

VeT: That's exactly the same results that we also had.

The reason of the problem was simply that your SED apparently has F5 assigned to Debug Run. The keys shown in the menus are only the default assignments, not the current assignments. So when pressing F5, you were probably starting a debug session all the time. Then the memory gets used up soon.

You can change the assignment in Options / Customize Hotkeys.

The different values on SED's first and second start came from memory fragmentation. This is absolutely normal.

Thus, I think the mysterious memory issue is now finally solved.

Yep. Thank you for your time

//You can change the assignment in Options / Customize Hotkeys.
Can you set this by default? Its not hard for me to change, but for others, who don't see this topic, it would be usefull.


//The different values on SED's first and second start came from memory fragmentation. This is absolutely normal.
Understood.

But what about Debug Run? Would you improve it in the nearest time?