Enhacement request: Big red "Stop execution" button, as well as "Garbage Collect" or "Release Memory".

[GoogleCodeExporter]

Sometimes network execution stalls due to bad coderunner code, bad
parameter choice, or some other problem. There seems to be no way to stop
such an execution (except for killing DeVIDE).

Also, memory is often retained and not released before re-running a
network, and sometimes the new (re)run request starts allocating more
memory before freeing the old.  I request to add a feature releasing
non-essential memory (even if this means that certain inputs will need to
me re-read from disk on next run).

Furthermore: extremely useful piece of software! :-)

Using
v9.8.3784 64-bit on Windows7 x64

Original issue reported on code.google.com by [email protected] on 2 Dec 2009 at 11:03