There are various seemingly different segfaults when PulseView tries to run two or more protocol decoders at the same time (there are _no_ issues if two or more are run one after the other).
It is not clear yet whether this is a PulseView/boost/mutex related issue or an issue in libsigrokdecode and/or Python.
See the comments here from more info:
Raising severity, this causes issues for multiple users in various circumstances.
We basically need something in PulseView that prevents (for now) that multiple decoders are run at the same time.
*** Bug 560 has been marked as a duplicate of this bug. ***
*** Bug 481 has been marked as a duplicate of this bug. ***
Note: while trying to replicate the issue I actually couldn't at first. Using one of my measurements and two SPI decoders, one decoder is blocked until the other one is done decoding. No segfault there.
So I can't say that preventing two decoders is the best solution atm, it may turn out that there's some kind of race condition being the culprit. I'll look into it.
*** Bug 746 has been marked as a duplicate of this bug. ***
Fixed in a1a3656b4e18cb9fc078a51bf4256066ee307620, thanks a lot!