Memory leak with Engine.loadAudioFilesIntoPool
-
@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:
const irs = Engine.loadAudioFilesIntoPool();
You're calling this in
on init? -
Yes. Is there a better way?
-
@Elezeid Nope, that's correct.
-
@d-healey Dang, I thought there was gonna be an alternative
Thanks anyway. I'll check back periodically hoping that someone has a solution or workaround.
-
@Elezeid Are you 100% sure it's caused by that function call?
-
@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:
Engine.loadAudioFilesIntoPool();
Are you sure you aren't calling this function anywhere else in your code?
-
I would probably first check to see if changing 'save in preset' for your combobox changes anything. Depending on how you're using your combobox that might help.
I would probably next, check on anything calling .changed(); on your combobox....
ie; if you have a rogue 'next/previous' button calling .changed(); at the wrong time.
def sounds like you have a weird loop somewhere.
@dannytaurus said in Memory leak with Engine.loadAudioFilesIntoPool:
Are you sure you aren't calling this function anywhere else in your code?
Engine.loadAudioFilesIntoPool();and this
-
@d-healey Yes. When this line is commented out, the issue is gone.
@dannytaurus Yes. I used ctrl+F to make sure.
@Chazrox there aren't any other functions like that tied to the combo box, the script is copied line for line from one of David Healey's tutorials. It's possible that it's become outdated?
I'll try unchecking "save in preset" but it's sort of an integral component of my presets, so if that does fix it, then I'll be in some trouble haha.
-
@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:
I used ctrl+F to make sure.
That only searches the current view, did you check all scripts in your project and all callbacks? There is a Find All Occurrences tool (ctrl + shift + f) that might help. However I doubt this is the issue since you say commenting out that line solves it.
-
@d-healey Thanks David, unfortunately this is indeed the only occurrence.
Am I really the first to run into this issue? If so, that definitely suggests user error of some kind, but I really don't know where I might have gone wrong!
-
@Elezeid said in Memory leak with Engine.loadAudioFilesIntoPool:
Am I really the first to run into this issue?
First one to report it at least, I haven't tested for it though.
