what was the memory issue

Now I understand it ALL :-).

This is the most common cause of memory problem with max patches.

ALL DIFFERENT STRINGS OUTPUTTED TO ANY OUTLET BY ANY OBJECT IN ANY PATCH TRIGGERS ALLOCATION OF ONE HASH IN THE MAX SYMBOLS TABLE.
THIS MEMORY WON't get FREED EVER, THAT IS UNTIL MAX QUITS.

But this is "cloudy" explanation for someone... including me at some point (what is the max symbol table???) so here it the PRACTICAL VIEW :
Are you familiar with the max size trick?
create an empty message and have it's text be
; max button
(respecting the spaces)

Now when you click it the MAX window will tell you the exact number of hashed symbols.
It's that simple rule :
If ithe number increases in some constant way then your patch has a memory leak problem
It will crash if let run, when memory in no more available.

The solution in our case was to avoid ever variating strings from circulating in the patch objects, making the relevant "string  things" inside some js object, never passing them to some outlet.


It might be your problem, and your solution