In fact there is a memory leak when you run a debug session. Every debug run consumes memory that is allocated by the script compiler and not released. But this does not affect the stability of the program, and does not happen in normal mode.

There were many reports that SED consumes a lot of memory. But we could never find a PC environment where this really happened. I've always asked if this was dependent on the script, and if so, to send that particular script to support so that someone else can reproduce this problem.

But we haven't yet received anything. So this problem is still a phantom.

Anyway, when you think you found a real memory leak, just make a bug report with the usual information:

- Does it happen a) only with your own script, or b) with all scripts?
- If a), strip down your script until the problem disappears. The last removed function then contained the problem - let us know details about it.
- If b), give a detailed description of your PC configuration, the circumstances, and how you measured the memory problem.