Bug 181 - Various issues when running multiple PDs at the same time
Summary: Various issues when running multiple PDs at the same time
Status: RESOLVED FIXED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Protocol decoding (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: High blocker
Target Milestone: PulseView 0.3.0
Assignee: Nobody
URL:
Keywords:
: 481 560 746 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-10-18 14:54 CEST by Uwe Hermann
Modified: 2016-02-11 15:14 CET (History)
5 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Hermann 2013-10-18 14:54:54 CEST
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:
http://sigrok.org/bugzilla/show_bug.cgi?id=170#c4
http://sigrok.org/bugzilla/show_bug.cgi?id=170#c5
http://sigrok.org/bugzilla/show_bug.cgi?id=170#c6
Comment 1 Uwe Hermann 2015-08-21 17:57:49 CEST
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.
Comment 2 Uwe Hermann 2015-08-21 17:59:15 CEST
*** Bug 560 has been marked as a duplicate of this bug. ***
Comment 3 Uwe Hermann 2015-08-21 18:02:53 CEST
*** Bug 481 has been marked as a duplicate of this bug. ***
Comment 4 Soeren Apel 2015-11-05 22:24:14 CET
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.
Comment 5 Soeren Apel 2016-02-02 18:53:57 CET
*** Bug 746 has been marked as a duplicate of this bug. ***
Comment 6 Uwe Hermann 2016-02-11 15:14:39 CET
Fixed in a1a3656b4e18cb9fc078a51bf4256066ee307620, thanks a lot!