On Mon, Apr 27, 2009 at 6:27 AM, IOhannes m zmoelnig <[email protected]>wrote:
> > first of all, this bug in Gem has been fixed in recent SVN (after your > initial bug-report) > the obvious solution is to run the hottest Gem (no release out, though; so > you have to compile it yerself) > > and since it is (was) a bug in the implementation of Gem, there is no way > you can "fix" it in Pd. the only workaround is to restart Pd (which will > free all stray memory). "unloading" does not work, because the memory had > been lost. Is this also bug with pix_film? I used pix_film for permanent installations to load hundreds of thousands of films over years without running into this problem. The same patch also had large pix_buffer objects that are stable in RAM usage.
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
