Re: [Jack-Devel] [LAU] jackd terminates on its own

PrevNext  Index
DateSun, 25 Jun 2017 14:20:55 +0200
From Kjetil Matheussen <[hidden] at gmail dot com>
To[hidden] at lists dot linuxaudio dot org, "[hidden] at lists dot jackaudio dot org" <[hidden] at lists dot jackaudio dot org>
Follow-UpKjetil Matheussen Re: [Jack-Devel] [LAU] jackd terminates on its own 
(cc to the jack-devel mailing list)



> jonetsu:


> > When using the latest Bitwig and loading several projects, enabling
> > audio for each one, playing it for a few seconds then loading another
> > one, playing it, so on so forth, jackd will steadily terminate, like
> > this:
> >
> > Jack: JackPosixProcessSync::TimedWait time out = 116080
> > Jack: JackPosixProcessSync::TimedWait finished delta = 3668.0
> > Jack: JackEngine::ClientExternalClose ref = 2
> > Jack: JackEngine::ClientCloseAux ref = 2
> > Jack: JackEngine::ReleaseRefnum server quit
> > Unknown error...
> > terminate called after throwing an instance of
> > 'Jack::JackTemporaryException' what():
>
>
Hi, I just took a glance at the source code of jack2,
and when you get this message:

  "Jack: JackEngine::ClientExternalClose ref = 2"

...and you don't see any message about "Kill", it's the client
that has called jack_close(). So it seems like BitWig has called
jack_close() manually. However, the rest of the messages
indicates that something is wrong somewhere.
PrevNext  Index

1498393856.14544_0.ltw:2,a <CAC6niELiJ_x8AznbMDF+DzT6eJmg+Shob4goEoXNosJhONJueA at mail dot gmail dot com>