Hans-Christoph Steiner wrote:
a patcher. One thing I noticed while doing this is that pd (or is it
the OS?) doesn't free memory when objects are deleted from a patch.You also can't delete or change a .dll once Pd has opened it. Pd keeps
the object in memory and the file locked until it quits.
while this is not necessarily related to the memory usage of an external, it should rather read: "Pd keeps the object in memory and w32 locks the file until pd quits." and it should even rather read ("...and w32 attempts to lock...")
just yesterday i happily discovered that i could circumvent this locking, while having pd loaded an external and at the same time compiling this external and replacing the .dll-file (whether this makes english sense is another question which i cannot answer)
mf.ads.r IOhannes