#133 Abort on exit after switching audio to jack multi

[Xavier]

In Nio settings, switch from JACK to JACK_MULTI, works normally until ask zyn for exit, then it crash with

Jack reports error: jack_port_get_buffer called with an incorrect port 0
zynaddsubfx: /home/xs/brx/zynaddsubfx/src/Nio/JackMultiEngine.cpp:136: int JackMultiEngine::processAudio(jack_nframes_t): Assertion `buffers[i]' failed.

backtrace attached

[Xavier]

Thanks to you :)

From: Mark McCurry Sent: Tuesday, 17 May 2016 18:32 To: [zynaddsubfx:bugs] Reply To: [zynaddsubfx:bugs] Subject: [zynaddsubfx:bugs] #133 Abort on exit after switching audio to jack multi

• status: in-progress --> closed-fixed
• Comment:

Thanks for reporting the issue. I was able to replicate and the crash which could occur either during initialization or closing of the jack-multi output mode is now resolved.

The fix is now in git, though there is also an unrelated crash in the master branch, so you may want to wait a day or so before updating to the git HEAD.

---

[bugs:#133] Abort on exit after switching audio to jack multi

Status: closed-fixed
Group: v2.5.5
Created: Mon May 16, 2016 02:20 PM UTC by Xavier
Last Updated: Tue May 17, 2016 04:10 PM UTC
Owner: Mark McCurry
Attachments:

• jack_multi_on_quit (7.0 kB; application/octet-stream)

In Nio settings, switch from JACK to JACK_MULTI, works normally until ask zyn for exit, then it crash with

Jack reports error: jack_port_get_buffer called with an incorrect port 0
zynaddsubfx: /home/xs/brx/zynaddsubfx/src/Nio/JackMultiEngine.cpp:136: int JackMultiEngine::processAudio(jack_nframes_t): Assertion `buffers[i]' failed.

backtrace attached

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/zynaddsubfx/bugs/133/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Mark McCurry]

Thanks for reporting the issue. I was able to replicate and the crash which could occur either during initialization or closing of the jack-multi output mode is now resolved.

The fix is now in git, though there is also an unrelated crash in the master branch, so you may want to wait a day or so before updating to the git HEAD.