View Issue Details

IDCategoryLast Update
0008713bugs2021-05-22 15:37
ReporterL3br4ndAssigned To 
Status newResolutionopen 
PlatformMicrosoftOSWindowsOS Version10
Product Version6.6 
Fixed in Version 
Summary0008713: Ardour crashes when trying to delete a freshly recorded region directly after stopping the recording
DescriptionAfter stopping the recording, when ardour is calculating the .peak files (or whatever it does shortly after hitting the stop-button), it is possible to make ardour crash by trying to delete a region which already seems to have been processed (region is displayed and marked red) while other regions are still being processed.
Steps To ReproducePreconditions: unsure, more likely to occur in projects with sample rates >=88.2 kHz and >= 24 bit depth with multiple recorded tracks
1. Start a Multi-Track recording (e.g. 9 Tracks in parallel).
2. Hit the Stop button.
3. Click at the first region which is being displayed after recording and hit <DEL> while other tracks are still being processed.
Additional InformationProject contained 48 tracks of which 9 were used for recording (drums).
Samplerate: 96 kHz
Bit depth: 24 Bit
Defect was reproducible with ardour 6.6, 6.6.489(? unsure, nightly from 16.05.2021 CEST), 6.2 and 5.12 under windows 10.

AMD FX-8350
Project stored on a SSD
RME Digiface USB connected to Yamaha 01V96 via ADAT used to record 9 tracks @96kHz/24bit in parallel

Unfortunately it was not possible to get the logs although I followed your instructions regarding the gdb-console. I simply was not able to find the logs on my machine although I searched every possible documents folder on the PC. I tried to raise the waveform image cache hoping to speed up the process but it still takes several seconds at which the crash can be provoked.

Also seen with Ardour 6.6 under Linux in a 16 track project with 44.1 kHz samplerate and 32 Bit float bit depth but it is necessary to act very fast to provoke this since the time frame the system needs to process the regions is very small (Xubuntu 20.10, AMD FX-7500, 8GB RAM, RME Babyface in Class Compliant mode)
Tags6.2, 6.6, 6.6.489, crash

Users sponsoring this issue
Sponsors List Total Sponsorship = US$ 50

2021-05-18 20:00: L3br4nd (US$ 50)
Users sponsoring this issue (Total Sponsorship = US$ 50)



2021-05-18 21:00

administrator   ~0025873

Is there a file in %localappdata%\Ardour6\CrashLog\ ?


2021-05-19 19:09

reporter   ~0025875

Yes, there are :-) (18,607 bytes)


2021-05-19 21:34

administrator   ~0025876


The original issue should be fixed since 6.6-491, but there were a few follow up issues. Ardour 6.6-570 should no longer crash when deleting the region. Please test.

There's another issue in the crash-log that's seemingly unrelated (registering actions, crash directly at startup) that I don't yet have an explanation for.


2021-05-22 15:13

reporter   ~0025880

The crash is still reproducible with Version 6.7.4.
I tried to generate gdb-logs under linux, but the gdb console gets flooded with JackAudioDriver::ProcessGraphAsyncMaster: Process error
(see screenshots)


2021-05-22 15:37

reporter   ~0025881

I got a debug log under Windows...

Ardour-debug.log (63,484 bytes)

Issue History

Date Modified Username Field Change
2021-05-18 19:56 L3br4nd New Issue
2021-05-18 19:56 L3br4nd Tag Attached: 6.2
2021-05-18 19:56 L3br4nd Tag Attached: 6.6
2021-05-18 19:56 L3br4nd Tag Attached: 6.6.489
2021-05-18 19:56 L3br4nd Tag Attached: crash
2021-05-18 20:00 L3br4nd Sponsorship Added L3br4nd: US$ 50
2021-05-18 20:00 L3br4nd Sponsorship Total 0 => 50
2021-05-18 21:00 x42 Note Added: 0025873
2021-05-19 19:09 L3br4nd File Added:
2021-05-19 19:09 L3br4nd Note Added: 0025875
2021-05-19 21:34 x42 Note Added: 0025876
2021-05-22 15:13 L3br4nd File Added: Bildschirmfoto_2021-05-22_17-09-07.png
2021-05-22 15:13 L3br4nd Note Added: 0025880
2021-05-22 15:37 L3br4nd File Added: Ardour-debug.log
2021-05-22 15:37 L3br4nd Note Added: 0025881