View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006550 | ardour | bugs | public | 2015-08-29 11:40 | 2015-09-05 10:36 |
| Reporter | unfa | Assigned To | |||
| Priority | normal | Severity | block | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0006550: Nightly GUI lockup | ||||
| Description | I installed debug build to catch this bug, now that it happened I didn't see anything in GDB. IT seemed that Ardour is working fine, but it just suddenly stopped refreshing it's window and stopped reacting to user input. I pressed Ctrl+C to force-quit, then I got a backtrace in GDB. Afterwards I used 'thread apply all bt' in GDB to get more info. GDB log with all threads backtraces: http://pastebin.com/ucgHq718 I've cut out some redundant logs of threads starting and ending leaving (...) marks. The log was huge with that left in. | ||||
| Additional Information | I attach a screenshot. This is how the window looked like when I unmaximized in and maximized it again. You can easily see that Ardour's not redrawing the window. | ||||
| Tags | No tags attached. | ||||
|
2015-08-29 11:40
|
|
|
|
I just got this again. Ardour's window didn't respond to mouse or keyboard events (the transport was stopped when that happened so I don't know how was audio doing). I finally pressed Ctrl+C in the GDB terminal to kill it. I'm using a script that's asking for all treads backtrace. GDB produced this: http://pastebin.com/SfQ2JxV3 |
