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

Robin Gareus <[hidden]> writes:

> 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

Maybe, or have better logging in jack2. Inspecting several old lines on
each new log line is probably waste of CPU. Do you have a motivation to
implement such supersmart logger?

If this error log line sequence is generated in single thread, error
messages can be collected and then logged as a single line. Not sure how
viable such solution is in the C++ do-it-right (tm) land. C++ exceptions
are not universally accepted.

> Simply launching a new client (here jack_lsp) after supercollider
> crashed made the issue go away. no jack-engine re-start needed.

This indicates issue with jack2 itself. Either genuinely wrong logic
somewhere or it gets fooled by external events. IMO.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>

1310959862.24926_0.ltw:2,a <871uxo85ir.fsf at arnaudov dot name>