View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000724 | ardour | bugs | public | 2004-09-22 08:16 | 2008-11-20 23:58 |
| Reporter | slinkp | Assigned To | taybin | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000724: Still possible to crash after loop stop | ||||
| Description | It is still possible to get the crash-after-loop-stop behavior described at http://ardour.org/mantis/bug_view_page.php?bug_id=516 All I have to do is set the snap type to "None" and then select a very very small loop range (e.g. leave the left edge of loop range at 0 and set the right edge of the loop range at 01|01|N where N is less than about 600), press the loop button, and as soon as I hit "stop", kaboom. I did this by accident at least once - I wasn't looking for trouble, honest :-) This can be reproduced reliably with brand-new sessions - just create a single track and set a very small loop range. Note that if the click track is disconnected, I can get away with smaller loop sizes (e.g. 01|01|240) IMO a perfectly good solution would be to enforce a minimum loop size. I can't think of any use case for loop ranges as small as I've been testing. | ||||
| Additional Information | Maybe same issue as http://ardour.org/mantis/bug_view_page.php?bug_id=516 but i can't figure out how to comment on or re-open a closed issue. | ||||
| Tags | No tags attached. | ||||
|
|
sorry, i should've marked this as a Crash issue. |
|
|
it almost certainly is the same issue as that resolved bug. the problem was that looping around (using seamless looping) failed to reset an internal list of frame times where click sounds should be generated. this then broke some code assumptions. are you using seamless looping or not? |
|
|
i was wrong. this was a very nice bug to find. there was a which-thread-does-what issue that we haven't noticed before. this should clean up quite a lot of crashes when using loops. i will commit this later today. |
|
|
please comment on new behaviour. ardour 0.9beta20 contains these fixes. this bug will be marked resolved by the end of next week (november 5th) |
|
|
Sorry, I can still provoke these segfaults with freshly compiled ardour 0.9beta20.(Ardour/GTK 0.536.0 running with libardour 0.837.0). Select a range starting at 01|01|00 and ending at 01|01|200, then rightclick -> "range-> loop range", then click the stop button. Chance of segfault seems to be about 50% for me. If I keep repeatedly selecting "loop range" followed by a stop, I can so far always provoke a segfault within 3 tries. -PW |
|
|
I finally got around to trying this with 0.99 and it appears to be fixed. You can loop INCREDIBLY tiny ranges with no problem. e.g. from 00|00|00 to 00|00|01 works fine. sounds like an analog synthesizer :) |
|
|
Resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-09-22 08:16 | slinkp | New Issue | |
| 2004-09-22 08:16 | slinkp | => pw_lists@slinkp.com | |
| 2004-09-22 08:16 | slinkp | Name | => Paul Winkler |
| 2004-09-22 08:20 | slinkp | Note Added: 0001479 | |
| 2004-10-16 23:38 | paul | Severity | minor => crash |
| 2004-10-18 11:21 | paul | Note Added: 0001529 | |
| 2004-10-18 13:36 | paul | Note Added: 0001533 | |
| 2004-11-01 02:26 | paul | Note Added: 0001550 | |
| 2004-11-01 02:26 | paul | Status | new => feedback |
| 2004-11-01 05:22 | slinkp | Note Added: 0001554 | |
| 2005-12-01 03:55 | slinkp | Note Added: 0002391 | |
| 2007-02-14 22:09 | taybin | Status | feedback => resolved |
| 2007-02-14 22:09 | taybin | Resolution | open => fixed |
| 2007-02-14 22:09 | taybin | Assigned To | => taybin |
| 2007-02-14 22:09 | taybin | Note Added: 0003264 | |
| 2008-11-20 23:58 | seablade | Status | resolved => closed |
