This is actually an old issue that has not come up for some time and there have been many upgrades, updates and fixes to how we handle memory since then.
The most common occurance was after reloading during analysis, the process would not kick back in properly and would keep allocating to memory unnecessarily and eventually crash the app - this has not been true for some time, but I have left the idea open in case any user had experienced this, especially those with super large libraries, i.e. 50,000 tracks+.
Have you had any issues with this or MIXO crashing at all?
Jon
• 5 years ago
1
JRiNVENTOR
• 5 years ago
1
Jon
• 5 years ago
The most common occurance was after reloading during analysis, the process would not kick back in properly and would keep allocating to memory unnecessarily and eventually crash the app - this has not been true for some time, but I have left the idea open in case any user had experienced this, especially those with super large libraries, i.e. 50,000 tracks+.
Have you had any issues with this or MIXO crashing at all?
1