View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000714 | ardour | bugs | public | 2004-09-13 16:57 | 2008-11-20 23:51 |
| Reporter | ndv | Assigned To | paul | ||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000714: ardour crashes X when overworked | ||||
| Description | Recently I've been chopping up loops into small fragments, rearranging them and copying and pasting them all over the place. It workes fairly well but when I try to manipulate (move or delete) too many regions at once (I estimate around a hundred, maybe more), the hard drive starts heavily crunching, the GUI slows right down and then freezes, then I get a rather pretty screen effect where some random data has been sent to the display, which lasts a few seconds until either gdm comes up again (as if X was re-started) or I get an error message saying X couldn't start due to configuration errors, in which case I seem to have to reboot to get X back. | ||||
| Additional Information | things that might be relevant are that I'm using the most recent Planet CCRMA ardour, it happens under both gnome and kde, and I'm using the NVidia drivers for my graphics card, which is some species of GeForce 4. | ||||
| Tags | No tags attached. | ||||
|
|
Is this still an issue? |
|
|
I don't know if this still occurs as I haven't used ardour for a long time. If I have a chance over the next month or so I'll download the latest ardour and try to see if it still occurs, but I can't guarantee that I'll get to it. I have found that Ardour isn't the only program that does this sort of thing though (SuperCollider locks my system up as well if I try to do too much at once, and I think some other programs have done it in the past as well) so it might be something peculiar about running Jack in realtime on my system rather than ardour per se. |
|
|
its a JACK issue and its fixed in the latest release. JACK's watchdog used to kill the JACK process *group* and because of the way various distros start up X, this included the X server. this was fixed in JACK so that it no longer kills the process group, just the process. |
|
|
see notes. feel free to reopen if i am wrong. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-09-13 16:57 | ndv | New Issue | |
| 2004-09-13 16:57 | ndv | => nathaniel.virgo@ntlworld.com | |
| 2004-09-13 16:57 | ndv | Name | => Nathaniel |
| 2006-11-03 18:42 | taybin | Note Added: 0002638 | |
| 2006-11-03 18:42 | taybin | Status | new => feedback |
| 2006-11-06 13:31 | ndv | Note Added: 0002667 | |
| 2006-11-15 04:06 | paul | Note Added: 0002781 | |
| 2006-11-15 04:07 | paul | Status | feedback => resolved |
| 2006-11-15 04:07 | paul | Resolution | open => fixed |
| 2006-11-15 04:07 | paul | Assigned To | => paul |
| 2006-11-15 04:07 | paul | Note Added: 0002782 | |
| 2008-11-20 23:51 | seablade | Status | resolved => closed |
