Mouser,
Seeing as some programs leak memory (something we are all used to...) it would be nice if we could set a taming limit on memory usage
Because the only real way to fix this situation is to restart the process it would be good if that was allowed
The only caveat would be that the process would need to have saved its state and restore it on startup again (so it isn't useful for everything)
If you do implement this it would be useful to be able to choose Restart based on one (or more) of several different memory thresholds
I will refer to the values as they are displayed by Process Explorer (ex:sysinternals and now MS) because that is a richer set of datapoints
Virtual Size can sometimes be useful as an indicator, much more useful is Private Bytes, Working Set Size and Working Set Private
Thanks for a very useful program... this would potentially make it even more useful
Seeing as some programs leak memory (something we are all used to...) it would be nice if we could set a taming limit on memory usage
Because the only real way to fix this situation is to restart the process it would be good if that was allowed
The only caveat would be that the process would need to have saved its state and restore it on startup again (so it isn't useful for everything)
If you do implement this it would be useful to be able to choose Restart based on one (or more) of several different memory thresholds
I will refer to the values as they are displayed by Process Explorer (ex:sysinternals and now MS) because that is a richer set of datapoints
Virtual Size can sometimes be useful as an indicator, much more useful is Private Bytes, Working Set Size and Working Set Private
Thanks for a very useful program... this would potentially make it even more useful