<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Heya,</div><div><br></div>OK that was badly phrased.  It's not a leak, it does not grow, and is the same size each time pulseaudio is launched.<div><br></div><div>I presume the shm is created with the size of memory that is preallocated.  Here's what would be useful to know.</div><div><br></div><div>What is the basis for the decision to preallocate that amount?</div><div><br></div><div>If the number of streams expected to be active at any one time is limited, could the pre-allocation reasonably be reduced?</div><div><br></div><div>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?</div><div><br></div><div>Or if these values are unknown, should I just tool around and keep reducing the amount pre-allocated until the audio stack fails?</div><div><br></div><div>Thanks!</div><div><br></div><div>Nick</div><div><br></div><div><br></div><div><br><div><div>On Sep 30, 2008, at 9:42 AM, Nick Thompson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Heya,<div><br></div><div>On both x86 and on an arm system there appears to be a huge shm file:<div><br></div><div><blockquote type="cite" class=""> <font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px">/dev/shm<br>-r-------- 1 nick nick 67108888 2008-09-29 09:33 pulse-shm-319812569<br> </span></font>  </blockquote><br></div><div>This is with pulseaudio 0.9.12</div><div><br></div><div>Is there any explanation for this somewhat large file?</div><div><br></div><div>Thanks!</div><div><br></div><div>Nick</div><div><br></div></div></div></blockquote></div><br></div></body></html>