Heya, OK that was badly phrased. It's not a leak, it does not grow, and is the same size each time pulseaudio is launched. I presume the shm is created with the size of memory that is preallocated. Here's what would be useful to know. What is the basis for the decision to preallocate that amount? If the number of streams expected to be active at any one time is limited, could the pre-allocation reasonably be reduced? Is the preallocation an amount per expected stream (presumably based on the buffer sizes usually being requested) plus some overhead. Any idea what these values are? Or if these values are unknown, should I just tool around and keep reducing the amount pre-allocated until the audio stack fails? Thanks! Nick On Sep 30, 2008, at 9:42 AM, Nick Thompson wrote: > Heya, > > On both x86 and on an arm system there appears to be a huge shm file: > >> /dev/shm >> -r-------- 1 nick nick 67108888 2008-09-29 09:33 pulse-shm-319812569 > > This is with pulseaudio 0.9.12 > > Is there any explanation for this somewhat large file? > > Thanks! > > Nick > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20080930/ecb3d444/attachment.htm>
