[ardour-dev] Another memory leak in current cvs

[Paul Davis]

>trying with valgrind but the dsp hits 100% almost straight away (even on a 

totally normal.

>small session any mouse movement pushes dsp load up pretty high) and if i try 
>anything ardour gets disconnected from jack (even running non realtime) and 

be sure to increase the client timeout to a very large value. 10000 is good.

>although valgrind memory consumption grows (to 92.2% when i close the 
>session) I dont think it hits the point to trigger the memory leak - the 
>graph seems to indicate no leak anyway.  

try it again with the larger client timeout.

--p