View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005716 | ardour | bugs | public | 2013-10-07 21:23 | 2013-10-15 19:41 |
| Reporter | Leatuspenguin | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Summary | 0005716: Recent builds of Ardour are regularly zombifying when using Jack 1 | ||||
| Description | This started happening only recently. It is still an issue currently with revision 3.4-199-gd742553. This only happens with Jack 1. I have tried it with Jack 2 and it doesn't happen there. I keep getting this message from Ardour - "[ERROR]: JACK: zombified - calling shutdown handler" It happens so often that it has made recent builds unusuable. It can and sometimes does happen before I even get anything done in a session. Adding tracks is enough to cause this issue and it seems, if i reconnect from within Ardour after it happens, that the next action can again cause it to throw up the error message. Sometimes it doesn't happen straight away but once it does throw up the error, reconnecting seems futile as it appears to happen within a matter of seconds again. When it does happen, qjackctl gives me this message - 21:54:05.311 JACK connection change. 21:54:12.174 XRUN callback (1). subgraph starting at a2j timed out (subgraph_wait_fd=18, status = 0, state = Finished, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.981 msecs internal poll failure reading response from client ardour to a xrun event 21:54:12.177 JACK connection graph change. 21:54:12.320 JACK connection change. The terminal read out when this happens is - write failed, drop flushed note off on the floor, time 47 > 0 JACK HALTED: zombified This message repeats over and over, increasing time value until Jack halts. Jack doesn't appear to be shutting down as I can load up other Jack programmes, even the 3.4 binary and playback a session from there, while my self build is still hanging and unable to reconnect for any length of time before zombifying again. I have tried using the --nozombies option for starting up Jack but it doesn't make any difference. As I said, it's only a recent issue and nothing has changed with my system otherwise. The fact that the 3.4 binaries work as this issue is happening have lead me to believe it is possibly some issue with recent builds. | ||||
| Tags | No tags attached. | ||||
|
|
I haven't had problems with this issue for awhile now. More recent builds seem to have fixed the issues i was having so i'll mark this as closed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-10-07 21:23 | Leatuspenguin | New Issue | |
| 2013-10-15 19:41 | Leatuspenguin | Note Added: 0015385 | |
| 2013-10-15 19:41 | Leatuspenguin | Status | new => closed |
| 2013-10-15 19:41 | Leatuspenguin | Resolution | open => fixed |
