Methodology for testing/finding memory leaks in Cubase?

Cubase
1

I’m building my master template and testing as I go, and it seems that I’m having a problem where after some amount of time, even if just idle, the project becomes unstable.

This could be a lot of things, including a CPU/cooling issue… but closing the project and re-opening it and the problem goes away (even without restarting Cubase), which leads me to believe it is a memory leak issue.

What is the best/is there a methodology to testing and analyzing if this is the case and what is causing it.

I have some complex daisy-chained chained routing in the template many levels deep

and I have many plugins pre-loaded.

I guess my first test would be loading the project in a safe-state/preferences-disabled state.

Thanks

2

A memory leak wouldn’t really cause instability over time unless you have a lot of memory pressure on the PC because you are already close to the limit. In that case, you’ll see the app’s working set continue to rise over time, and you’ll see Windows starting to thrash and page.

But even a rising working set is not necessarily indicative of a memory leak.

I would start from the problem and work out, vs starting from a possible cause and try to diagnose that.

Pete
Microsoft