using MallocDebug i can see that InitializeTimeInfo called from
AudioIOProc in portaudio/pa_mac_core/pa_mac_core.c allocates memory
on each io cycle. this is then passed as a parameter (timeInfo) to a
callback routine. i'm not familiar with portaudio and thus don't know
who is expected to release the memory (pd or portaudio). i guess this
would be the job of portaudio?
lorenz
Am 05.11.2005 um 14:31 schrieb Enrique Erne:
On Nov 5, 2005, at 2:02 PM, Mathieu Bouchard wrote:
On Sat, 5 Nov 2005, Enrique Erne wrote:
On Nov 5, 2005, at 12:55 PM, Mathieu Bouchard wrote:
On Sat, 5 Nov 2005, Enrique Erne wrote:
now something I'm little bit more concerned: I've seen (activity monitor) that pd needs more and more memory. it starts about
2.7 MB and without doing anything it just increases about 20kb/second .
after two hours it took about 150 MB memory and was still increasing.
this happens on osx 10.3.9 using miller's pd without any patches or libs is
this a bug ? do you have the same behavior ?Which half of PureData is causing the problem? Is it "pd" all
lowercase (server) or "Pd" capitalized (client) ?it's the lowercase "pd" , which is going up and up. now it's over
317 MB . wonder what happen when it reaches the limit.When it reaches the limit it surely just crashes. Depending on
what your limit is, it'll swap a lot before reaching the limit.I can't test it myself because I don't have a mac.
I would suggest running Valgrind but it's a Linux-only program.
What would be a good equivalent to that on OSX? There's a neat program called
"Shark" on the Developer Tools CD, but I don't recall whether it can
detect memory leaks.I'm not familiar with that, actually I'm not familiar with c- programming compiling etc.
Which version of Miller's pd exactly??
It is Pd version 0.39-1 compiled for Macintosh. on OS X 10.3.9
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list