Does anyone else get this? Its never really bothered me that much, but I’m hoping to get onto next stage of mixing, and making smaller adjustments across a few tracks, and it will get a bit annoying.
If I start a new session, close Ardour, open it, load another, the everything works fine.
If I go to load recent, then select another session while its already running, then it nearly always crashes.
We can’t fix such things unless you file bug reports (which in this case will also need backtraces via the instructions in Debugging Ardour | Ardour DAW)
I have this issue but assumed it was plugin related… may also be related to wine. Are you running wine? If so, I noticed that cancelling the wine environment, crashes the wine related plugin which in turn crashes Ardour but in this instance I believe it is wine not Ardour.
I strongly recommend to follow Paul’s advice to file a bug report. This willl help for later backtrace if fixes get in and maybe cause other issues. And if you file it, please provide the link here so that others can follow. That would be very helpful.
Since many others do not experience this, it is quite sure that each situation where it happens need to be investigated deeper. Many possible issues can cause this “visible” unwanted behaviour for some users. So it is not automatically the same root cause showing the same result for all of you. Again, as Paul stated: a detailed issue report would really help. There are many reports on different DAWs that they crash often on session close. And the reports and root causes differ a lot. So it will be the same here and will likely much have to do with your personal setup in conflict with other things. Audio drivers, sessions with different sample rates, or some “challenging” plugins used in both sessions which need to reload and are challenging on load of your system, session folder permissions, your systems performance settings, AudioAssault, “auto-detect” and “calibrate” setttings for the used audio system, to just count a few of many on each of the commented. Also, does the sessions hold scripts, is the CPU high on the open session, etc, etc. Many informations required here.
I know that users often hesitate to get thru the steps of reporting issues, but on the end it often helps far more and also others when the reports have been made. On the end, it is quicker than guessing for years what causes it or in case it fades, why it appears again later.