I ran Audacity under valext and here is the graph of real memory use:
And here is the soft and hard fault count:
My surmise as to what you can see here? Lots of initialising – with memory use shooting up and down – though the low level of hard faults suggests much of this is from libraries already loaded in the system. Then pages getting swapped out as nothing happens – audacity did not actually display a window – not sure why – I killed it after it had been running for about two and half minutes of virtual time (around 24 hours of wall clock time) as that was more than enough time to produce something on screen!
Still, as a first test of the tool, that was not bad.
- How does the operating system use its memory (wiki.answers.com)