View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009729 | ardour | bugs | public | 2024-06-21 08:05 | 2024-06-24 11:23 |
Reporter | johne53 | Assigned To | |||
Priority | normal | Severity | crash | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Microsoft | OS | Windows | OS Version | 10 |
Product Version | Mixbus 10.x | ||||
Summary | 0009729: Double-click crash affecting the Audio/Midi Setup window | ||||
Description | I discovered this in Mixbus10 on Windows but I guess it might also affect Ardour and the other platforms. | ||||
Steps To Reproduce | Launch Mixbus, select a session and click 'Open' (to show the Audio/Midi Setup window). If you now accidentally double-click 'Start' instead of single-clicking, Mixbus will crash. | ||||
Additional Information | If I run a Debug build here, I see an assert in the function 'Splash::pop_front_for (Gtk::Window& win)' | ||||
Tags | No tags attached. | ||||
|
An interesting development this morning... I noticed a comment in 'Splash::pop_back_for()' which suggests that this feature might work differently for different platforms - so I tried the Mac version which (Initially) seemed to give me the same problem but I realised it'd in fact hung somehow, rather than crashing. It gave me the same message but with the Audio/Midi dialog's 'Start' button still visible - so I pressed 'Start' and realised that everything then continued normally. So I tried the same thing on Windows and saw the same behaviour! So the real problem is that double-clicking (in a Release build) will in fact hang the session load - whereas in a Debug build it'll trigger an assert. |
|
This seems to be connected to the fact that double-clicking 'Start' doesn't cause 'ArdourDialog::on_unmap()' to get called - whereas single-clicking does. That's about as close as I can get here. |