Crashes & Crash Reports
Crashes in Mixbus should be very rare. We've worked very hard to eliminate them. But we can't guarantee perfect operation on every setup.
On MacOS, you can generate a "crash report" which can often help us pinpoint the cause of a crash. To do that, please click "Generate Report" when Mixbus crashes, then click "Show Details", and then select-all/copy/paste the text of the crash into an email for us. This will usually (but not always) tell us exactly where the crash occurred, whether it is inside Mixbus itself, a plugin, or the OS.
Unfortunately, Windows does not provide us the same level of crash-reporting and troubleshooting that Mac does. So it can be hard to determine what is causing the crashes on Windows. We can send a "debug" version of Mixbus that will provide us a more explicit report, but (a) it takes some extra steps on the user's part, and (b) sometimes it still isn't clear how to fix the problem.
Generally speaking, crashes aren't random. They usually come shortly after an operation that, over time, you can learn to recognize. This might include:
a) A sequence of operations that we didn't anticipate: For example, we recently found a crash when you try to use the gain up/down shortcuts, while you are dragging a selected region in the editor.
b) An automatic event such as Mixbus's auto-backup (every 2 minutes), or a virus-checking scan that is somehow triggering an unexpected crash.
c) Plugins: plugins are third-party code that we load into our program. This means they share the same memory. A plugin that corrupts the program memory can result in very odd behavior or crashes in Mixbus. Generally the only way to detect this is to take notice of the performance when you start using a new plugin. If you are a new user to Mixbus, then "all" of your plugins should be considered new.
Once you've recognized the cause of a crash, we can help you consider how to avoid it. Or, if we can recreate the crash here, we can implement a fix inside Mixbus so the crash won't happen in the future.