Closed HaHeho closed 3 years ago
These changes https://github.com/jackaudio/jack2/commit/f3e8a6bc6b57c15e47de6cc8640764e439594cbd might be the cause?
Thanks for the report!
I can reproduce the problem, but I don't really understand the details of it.
I've left a comment at https://github.com/jackaudio/jack2/pull/578#issuecomment-707338266.
If we don't find a solution that's compatible with both old and new JACK versions, I think it would be best to simply hard-code the constants in the Python code without looking at the JACK library.
Good, thank you.
Unfortunately I am not able to contribute to the discussion or a fix at the moment since my C is too rusty at this point and I have not looked into cffi
so far.
The change also caused other application to break. Therefore it was reverted in the most recent 1.9.16 release. We will have to keep an eye on when they are going to reintroduce the change that initially broke the Python bindings.
FYI, this time I installed via the newly available installer (macOS and Windows) which worked without problems. https://github.com/jackaudio/jack2-releases/releases/tag/v1.9.16
Can confirm. The reverted changes in upstream JACK2 (v1.9.16) allow this binding to work again without SEGFAULTing.
Hey, very recently I experience this segmentation fault whenever trying to import the package. I have no idea yet what component caused the change in behavior. The most probable candidate is building more recent versions of
jack2
from source. Maybe investigating this can help to solve a bug here or upstream.This is the most basic case where the segfault happens (empty environment, basically not more than
pip install
):Using
faulthandler
reveals that it happens during the decoding of"JACK_METADATA_"
during import: