low-memory testing

[Albert Cahalan]

Things tend to go bad in low-memory conditions. I'm trying to
reproduce bug #4355, which I suspect to be DMA going to the
wrong location when memory runs low. (please help) It is common
for low-memory conditions to corrupt filesystems and databases.

A decent way to cause trouble is the Measure activity.
It currently does both audio and video while leaking memory.

Other interesting activites include Record (xvideo), TamTam
(audio out), and Journal (keeps a critical database). For some
or all of these, alternate ways to leak memory are needed.
Note that memory must be written to for it to matter.

Failure to find these problems now will lead to getting lots
of seemingly unreproducable bug reports from deployment.