Open deadpahn opened 9 months ago
If I knew where the junk is coming from, I could just not put junk in there in the first place - and if I don't know where the junk is coming from, I can't really get rid of it without damaging actually required data in memory anyway.
from what I recall, sometimes if I load something like a sample, even if its tiny, it will max out the ram. its a rare thing I cant really reproduce. Maybe in the debug build it can dump the contents onto disk to help you debug the issue?
Sometimes there is a bug in which the memory bar fills up all the way and I can't save the song. Just happened and I lost a banger :(
Was wondering if it's possible as a work around to be able to add some sort of memory check/flush button in the options to get rid of whatever junk got put in there by mistake? It preserves the samples and pattern/song data but maybe deletes the undo buffer and anything else that shouldn't be there?
Thanks