Dear all, I'm looking into valgrind + massif, to track down where the massive memory requirements of jackdmp (Jack2) come from. I'm new to its usage and perhaps I miss something regarding memory attribution with the top command, but here's what I face: According to top, jackd takes 216Mb VIRT, 147M RES, 96Mb SH. If I run with valgrind --tool=massif the log I get from massif is a mere 6Mb of memory. Either valgrind is right and I do not know what the top figures are about, either valgrind can't track down all that large memory locked by jack. According to my knowledge jack is used to get slightly less than 100MB, so I guess the second is the most probable answer.
FYI: Jack runs with 4 threads, one of which is in a privileged PAM group with unlimited memory locking and realtime (SCHED_FIFO) priority. Maybe massif can't see the thread which allocates most of the memory? Regards Leonardo -- Dr. Leonardo Gabrielli, PhD student A3Lab - Dept. Information Engineering Università Politecnica delle Marche via Brecce Bianche 12, 60131, Ancona, Italy Skype: leonardo.gabrielli Web: a3lab.dii.univpm.it/people/leonardo-gabrielli <http://a3lab.dii.univpm.it/people/leonardo-gabrielli> ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
