Am 01.04.2009 um 15:14 schrieb IOhannes m zmoelnig:
Max wrote:here is the same thing with pix_multiimage instead. it will crash pd a little bit later than the version with pix_image.i guess it is crashing right after you try loading 1000000 images (or so) into RAM.what do you expect?
no it isn't the problem of a sequence wich is too long. it is the problem that the old sequence doesn't get erased from the ram.
(if you look carefully, you might also notice that [pix_write] gradually fills up your harddisk. this is no bug either ;-))
that aint a problem either.
or am i missing something obvious (it seems so, as i cannot reproduce the memleak you report with [pix_image] either).
well, obviously you are missing something. i hope someone can reproduce that with the attached patches.
run top to see the memory beeing eaten by pd. at least on os x with GEM: ver: 0.91.3 'tigital' GEM: compiled: Feb 23 2009
timelapse_multiimage.pd
Description: Binary data
timelapse.pd
Description: Binary data
PGP.sig
Description: Signierter Teil der Nachricht
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
