memory leak: host system crashes after prolonged use with jack

[Jeremy]

While utilizing jack (www.jackaudio.org) on the host, and virtualbox on the host, the system can becoe unusable because of a memory leak.

how to reproduce:

On the host machine, in this case running Linux I386 Debian Wheezy, start jack and the following clients:

ecasound (for transporting audio from jack to a remote server) mpg123 (for ingesting audio)

Next start the virtualbox guest. As long as mpg123 is providing content into the jack system, there is a small memory leak, about 100k a second. No process takes ownership of the loss of memory, but total memory ithat is used in 'top' reports the leak. The memory does not appear in the buffers or cache columns, and after a few hours several processes are killed with OOM killer, rendering the host machine unusable if dhcpd or bind is terminated. Eventually, the machine becomes unresponsive to all network traffic and requires a hard-reset to bring it back to life.

If mpg123 is connected to the jack system, but not providing audio, the machine can run for days without incident and no apparent memory leak. If the guest is never started, and if mpg123 is providing content, the system is stable.

If Virtualbox is running, but jack and friends are not, the system runs fine for days at a time--it is only when mpg123 is providing content. I also tried this with jack_simple_client, various versions of jack, the alsa and dummy backend drivers, but the problem is still present--only when the virtual guest is running and when an audio client is providing audio for jack does this problem appear.

[Jeremy]

VBox.log