View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002749 | ardour | bugs | public | 2009-06-24 12:25 | 2020-04-19 20:14 |
| Reporter | nettings | Assigned To | cth103 | ||
| Priority | normal | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Platform | openSUSE 11.1 on core2 (32bit) | OS | Linux | OS Version | 2.6.29.5-rt21 |
| Product Version | SVN/2.0-ongoing | ||||
| Summary | 0002749: GUI thread becomes unresponsive after setting (or maybe dragging) automation points. | ||||
| Description | Sometimes, when setting or dragging automation points, the automation tool cursor starts flashing madly and the GUI thread becomes unresponsive, apparently spinning in a tight loop. Not strictly a crash, since the audio engine keeps going (i.e. if you were rolling at the time of the problem, the sound will continue flawlessly), but the only way out of this situation is to kill ardour. Ben Loftis has acknowledged having seen the same recently. | ||||
| Steps To Reproduce | It does not happen all the time. I *think* it might be an unintentional double-click plus drag or some other corner case. Just try to make a complex edit of automation and wait... I'll update this as I stumble upon it again. | ||||
| Tags | No tags attached. | ||||
|
|
during a mixing yesterday, this bug has occurred 4 times in 2 hours, each time requiring manual killing of the ardour process. top showed it was chewing up 100% of one of two cores. on an up machine, i wonder if this has the potential to bring down the machine - will test on my single-core amd box once i'm back home. it is definitely connected to the setting or dragging of control points. moreover, there seems to be another (probably unrelated) bug that causes ardour to get confused wrt to the position of later control points when editing something in the middle of the control graph... |
|
|
The problem has to do with the popup timecode "text" that appears when you are editing the points. the text apparently steals focus, then gets into a loop of gtk enter/exit events with the underlying edit point. Paul is looking at a deeper fix for all potential occurrences of this problem, but here's a hack to fix it temporarily: in editor_mouse.cc around line 1302, find the lines "set_verbose_canvas cursor" and "show verbose canvas cursor" and comment out those lines. There is a side-effect to this: the canvas cursor will not appear when you hover the mouse over the control point, you have to actually click the point before its value will be displayed. |
|
|
hmm. couldn't reproduce this in a test session with current svn (r5499). if someone has worked on this: maybe you fixed it :D. if not, i don't know... [Update:] i think i saw the original bug on a dual-core machine, and all my ardour work in the last 2 weeks has been on a single-core. so the above remark may not indicate anything useful... |
|
|
yep, this is ye olde "enter/display other widget/enter other widget/leave/hide other widget/enter/... ad infinitum" bug. no conceptual fix for this yet. one is needed ASAP. |
|
|
This should be fixed. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-06-24 12:25 | nettings | New Issue | |
| 2009-06-29 10:45 | nettings | Note Added: 0006196 | |
| 2009-06-30 21:46 | BenLoftis | Note Added: 0006201 | |
| 2009-08-13 17:28 | nettings | Note Added: 0006517 | |
| 2009-08-14 09:28 | nettings | Note Edited: 0006517 | |
| 2009-10-31 14:25 | paul | Note Added: 0007026 | |
| 2010-01-05 15:08 | cth103 | cost | => 0.00 |
| 2010-01-05 15:08 | cth103 | Note Added: 0007294 | |
| 2010-01-05 15:08 | cth103 | Status | new => resolved |
| 2010-01-05 15:08 | cth103 | Resolution | open => fixed |
| 2010-01-05 15:08 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:14 | system | Note Added: 0021937 | |
| 2020-04-19 20:14 | system | Status | resolved => closed |
