5’ve just been checking a patch that simply x fades between to patches and then uses create node to change patch, then x fades. It also writes a log to a txt file with append, that saves fps and available memory.
I started it running (changing patches every 5 seconds) and available memory was 157,544.448 Bytes, 5 hours later its was down to 10,326,016 Bytes. The memory footprint in task manager was at 250 odd MB at this point and fps was down to 10 from 40. This is a very simple patch so I can only assume theres a hole like a leaky bucket somewhere!
Luckily all the patches are pretty simple so I think I can load them all and simple fade them in and out for now, Im going to test that now!
Cat