Re: [Jack-Devel] [jack2] Client crash on MIDI mixdown when using multiple connections (#46)

PrevNext  Index
DateSat, 21 Dec 2013 09:39:16 +0100
From Stéphane Letz <[hidden] at grame dot fr>
Tojackaudio/jack2 <[hidden] at reply dot github dot com>
Cc"[hidden] at lists dot jackaudio dot org Developers" <[hidden] at lists dot jackaudio dot org>, jackaudio/jack2 <[hidden] at noreply dot github dot com>
Follow-Upthijz Re: [Jack-Devel] [jack2] Client crash on MIDI mixdown when using multiple connections (#46) 
Dmitry Baikov wrote this code… back in 2007. Not sure he even read this list anymore.

Any way for you to debug the code yourself with the test case you have?

St鰨ane 


Le 21 d飮 2013 ࠰5:41, falkTX <[hidden]> a 飲it :

> I'm having a crash (assertion failure) in latest git jack2 code.
> 
> it crashes during jack_port_get_buffer function.
> Running the app normally prints to terminal:
> jack_midi_dump: ../common/JackMidiPort.cpp:130: void Jack::MidiBufferMixdown(void*, void**, int, jack_nframes_t): Assertion `next_event != 0' failed.
> and through GDB:
> 0x00007ffff6af2302 in __GI___assert_fail (assertion=0x7fffe92e8fbb "next_event != 0", file=0x7fffe92e8fa0 "../common/JackMidiPort.cpp", line=130, function=0x7fffe92e8fe0 "void Jack::MidiBufferMixdown(void*, void**, int, jack_nframes_t)") at assert.c:101
> 
> I was able to get a simple test for the crash (in Linux).
> 
> 1. run any kind of jack-midi generator (sequencer, keyboard, etc)
> 2. run another client that has jack-midi-out, but this one doesn't need to output any events.
> (I'm using "jack_midiseq EmptySequencer 1 24000 0 60")
> 3. run "jack_midi_dump" twice
> 4. connect the midi generator out port to both midi-monitor in ports, same thing for midiseq
> 5. generate/play some events for a few seconds
> 
> a single or both jack_midi_dump tools will abort due to an assertion failure.
> 
> —
> Reply to this email directly or view it on GitHub.
>
PrevNext  Index

1387615060.5279_0.ltw:2, <B7329032-EF31-4CB9-87D3-FAFEEF6546B7 at grame dot fr>