View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010119 | ardour | bugs | public | 2026-01-11 09:01 | 2026-02-21 09:11 |
| Reporter | IndustrialPowerSound | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | Microsoft | OS | Windows | OS Version | 11 |
| Product Version | 8.12 | ||||
| Summary | 0010119: Ardour crashes after loading step "indexing plugins" when opening projects by clicking on the .ardour project files | ||||
| Description | Ardour crashes to desktop after loading step "indexing plugins" when opening projects by clicking on the .ardour project files. However, opening Ardour.exe and open projects from the "recent projects" list or browse projects not on the list works, and does not crash on the same step. | ||||
| Steps To Reproduce | On affected systems: click on any .ardour project file | ||||
| Additional Information | I reported this in the Ardour forums as well, and another user on MacOS responded they had the same issue there and suggested I open a ticket here, see: https://discourse.ardour.org/t/problems-opening-projects/112791 This phenomenon happened "over night" about a month ago; it was working fine until then and hasn't worked since. I had not done any updates to Ardour at that time, nor recently installed any new plugins, but I did try to reindex/rescan all plugins again anyway, without it solving the issue. I'm on an AMD Ryzen 7900x CPU with 64GB RAM, working off of SSDs (M.2 for OS/applications, SATA SSD for music projects). | ||||
| Tags | No tags attached. | ||||
|
|
I cannot reproduce this. Works fine on all 3 platforms with Ardour 9.0-rc2. Also the forum thread you reference is for Mixbus. .ardour sessions were never registered to launch Mixbus in the first place. I only have a handful of Plugins on Windows, so maybe the issue is somehow related to that? Sadly I don't know how one could debug that when launching Ardour like this, since interactive debugging is not possible either. |
|
|
I opened the forum thread under "installation & configuration" for Windows, didn't see anything about Mixbus, but someone "hijacked" the thread with a lot of Mixbus comments later; I always referred to Ardour. But this might be fixed in Ardour 9.0, then? I'm on 8.12. When's 9.0 planned? |
|
|
> When's 9.0 planned? There are no plans, it's ready when it's ready. It is currently in beta-test release candidate state. So it depends how how many bugs are reported and how fast they can be fixed. |
|
|
PS. You could try a https://nightly.ardour.org/ build (demo is fine and it be installed in parallel to Ardour 8). |
|
|
> This phenomenon happened "over night" about a month ago; it was working fine until then and hasn't worked since. I had not done any updates to Ardour at that time, nor recently installed any new plugins, but I did try to reindex/rescan all plugins again anyway, without it solving the issue. That is even more mysterious then. Does it affect all .ardour sessions? or only some specific ones? |
|
|
> Does it affect all .ardour sessions? or only some specific ones? I haven't come across any sessions lately where it didn't happen, so it's certainly affects all of my recent .ardour sessions, which also includes a couple of sessions I hadn't visited for several months. |
|
|
This seems to carry over to Ardour 9 for me as well... |
|
|
As x42 noted above, since this only happens when clicking on .ardour project files (apparently?) there's almost no way to debug this (which requires starting ardour from the command line) ... |
|
|
@paul, I hadn't tested starting Ardour from command line before, but as you suspected the project started without issue that way. It does indeed only happen when clicking on .ardour project files. |
|
|
Tech details: The problem happens only with specific soundcard drivers; that raise the thread priority of the calling thread even when just probing it. This later causes a problem with gtk not being able to create threads with elevated priority. When launching manually gtk thread init happens when the file browers (recent session) is realized and before the engine dialog is shown. It is still unclear how to best solve this. The driver raising the main application UI's thread priority isn't great either. PS. one can write a ,bat file for indirection to write debug output when opening a .ardour project |
|
|
@x42 I guess that makes sense, since this started happening after I upgraded my graphics card, which includes sound drivers (although they're not in use), from GeForce RTX 3060 to 5060. It did work for a while with that too, but then over night at one point stopped working, possibly then due to an automatic driver update. The soundcard I actually use is a really old Asus Xonar DX card, which no longer gets driver updates, and has been running the same drivers for years... I'll gladly try the .bat file approach to help give you more details, if you point me in the right direction as to what to put in it, and when and where to start it for it to monitor the behavior of clicking an .ardour project file. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-01-11 09:01 | IndustrialPowerSound | New Issue | |
| 2026-01-16 15:42 | x42 | Note Added: 0029724 | |
| 2026-01-16 16:16 | IndustrialPowerSound | Note Added: 0029725 | |
| 2026-01-16 16:32 | x42 | Note Added: 0029726 | |
| 2026-01-16 16:33 | x42 | Note Added: 0029727 | |
| 2026-01-16 16:58 | x42 | Note Added: 0029728 | |
| 2026-01-16 17:09 | IndustrialPowerSound | Note Added: 0029729 | |
| 2026-02-20 11:58 | IndustrialPowerSound | Note Added: 0029927 | |
| 2026-02-20 17:42 | paul | Note Added: 0029938 | |
| 2026-02-20 19:19 | IndustrialPowerSound | Note Added: 0029944 | |
| 2026-02-20 20:51 | x42 | Note Added: 0029961 | |
| 2026-02-21 09:11 | IndustrialPowerSound | Note Added: 0029966 |
