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.