Re: [Jack-Devel] jackd-logging -- was jackd2+ardour3 - tracking down "JackActivationCount::Signal value = 0 ref = INT"

PrevNext  Index
DateMon, 18 Jul 2011 02:26:46 +0200
From Robin Gareus <[hidden] at gareus dot org>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
CcJack devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToNedko Arnaudov Re: [Jack-Devel] jackd2+ardour3 - tracking down "JackActivationCount::Signal value = 0 ref = INT"
Follow-UpNedko Arnaudov Re: [Jack-Devel] jackd-logging -- was jackd2+ardour3 - tracking down "JackActivationCount::Signal value = 0 ref = INT"
Follow-UpStéphane Letz Re: [Jack-Devel] jackd-logging -- was jackd2+ardour3 - tracking down "JackActivationCount::Signal value = 0 ref = INT"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/17/2011 04:31 PM, Nedko Arnaudov wrote:
> Robin Gareus <[hidden]> writes:
> 
>> On 07/15/2011 06:38 PM, Stéphane Letz wrote:
>> [..]
>>
>>> But basically you are going to get *real* XRun error message in this
>>> case right?
>>
>> Yes. (BTW. Could one disable those as well? Does jack have a "quiet"
>> mode that only logs fatal errors?)
> 
> I'd be happy if xrun messages in the log file can be disabled, or better
> be single line so that a smart logger can collapse them (last message is
> repated 120398 times).

Maybe it's rather time for a smarter smart-logger :-)

xruns are not the only issue. I just managed to fill
~/.log/jack/jackdbus.log with 16MB of 4-line repeats:

Mon Jul 18 02:16:03 2011: ERROR: JackPosixSemaphore::Signal name =
jack_sem.1000_default_SuperCollider already desallocated!!
Mon Jul 18 02:16:03 2011: ERROR: JackFreewheelDriver::ProcessReadSync:
ResumeRefNum error
Mon Jul 18 02:16:03 2011: ERROR: JackAudioDriver::ProcessGraphSync:
ProcessReadSlaves error, engine may now behave abnormally!!
Mon Jul 18 02:16:03 2011: ERROR: JackActivationCount::Signal value = 0
ref = 1
Mon Jul 18 02:16:03 2011: ERROR: JackPosixSemaphore::Signal name =
jack_sem.1000_default_SuperCollider already desallocated!!
Mon Jul 18 02:16:03 2011: ERROR: JackFreewheelDriver::ProcessReadSync:
ResumeRefNum error
Mon Jul 18 02:16:03 2011: ERROR: JackAudioDriver::ProcessGraphSync:
ProcessReadSlaves error, engine may now behave abnormally!!
Mon Jul 18 02:16:03 2011: ERROR: JackActivationCount::Signal value = 0
ref = 1

Simply launching a new client (here jack_lsp) after supercollider
crashed made the issue go away. no jack-engine re-start needed.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4jfcYACgkQeVUk8U+VK0L75QCgmMVNVcLw6X1+EzLc+SfMjhrM
7SYAnAyrfx33eDoR2Nx7v4q2j8oxdYCs
=9IO/
-----END PGP SIGNATURE-----
PrevNext  Index

1310948834.10640_0.ltw:2,a <4E237DC6.9010707 at gareus dot org>