frank desben

I have a main patch, which dynamically loads poly patches, that each have different VSTs with bigger sample libraries in them). If I load anther patcher the memory is never freed completely, so that over time the memory gets piled up - even though no patches are loaded anymore.

Dear all,
I have a main patch, which dynamically loads poly patches, that each have different VSTs with bigger sample libraries in them). If I load anther patcher the memory is never freed completely, so that over time the memory gets piled up - even though no patches are loaded anymore.
Any tips, workarounds?
All the best
Frank

Dear all,
I have a main patch, which dynamically loads poly patches, that each have different VSTs with bigger sample libraries in them). If

memory-leak-poly-vst-dynamic-loading

One question would be is it due to the VST(s) or to Max. If you can make an example patch showing clearly the memory build-up (for instance a patch with a metro loading your vst/patch, etc.) , I suggest you send it to support, along with your information (Windows, Mac, etc.)

hm, that buffer or value incl content still exist when you unload a patch is normal. but i dont think that max has anything to do with a vst´s sample content.


hm, that buffer or value incl content still exist when you unload a patch is normal. but i dont think that max has anything to do with a vst´s  sample content.

OK, yes, I can create a patch like that. But it will also need a VST (in my case Kontakt with samples). 

Roman: It does not interfere with the samples - but everytime I open a patch with a Kontakt player and then unload it, about 100MB stays allocated / not cleared, so that with each iteration the RAM in the activity monitor increases, until Max is not working propperly anymore. 

At the end, even if I close the main patch, MAX still has about 4GB of memory allocated.

Shouldn't everything be freed if you close the patches?

OK, yes, I can create a patch like that. But it will also need a VST (in my case Kontakt with samples). 
Roman: It does not interfere with the samples - but everytime I open a patch with a Kontakt player and then unload it, about 100MB stays allocated / not cleared, so that with each iteration the RAM in the activity monitor increases, until Max is not working propperly anymore. 
At the end, even if I close the main patch, MAX still has about 4GB of memory allocated.
Shouldn't everything be freed if you close the patches?

by the way I am on Max OS 10.14.6, Max 8.1

Memory Leak (Poly, Vst, Dynamic Loading)