Audioplay is a cool little tool except for one thing, it's resident size
grows beyond what is healthy for a little program like it. Here's what
happens when playing a ~30mb wav:

After a few seconds:
USER       PID %CPU %MEM   VSZ  RSS TT  STAT STARTED       TIME COMMAND
pooka    10629  1.0  0.8    20  520 pc  S+    9:30PM    0:00.02 audioplay a.wav 

And after a few minutes:
pooka    10629  0.2 35.0    20 22788 pc  S+    9:30PM    0:01.52 audioplay a.wav

-> No fun at all.
I guess this is the same thing that happens to mpg123 when compiled with
-DREAD_MMAP, it's resident size also grows annoyingly big. Is there
something wrong with the software, or is my system just plain sick?

-- 
  "Never underestimate the power of the Lite side of the \Source/"
 Antti Kantee   /       NetBSD        \  Citius, Altius,  \    / o
<pooka@iki.fi> / http://www.netbsd.org \     Levytys       \  /  |
______________/ Free Multiplatform UN*X \___________________\/__ |