Bug 924 - Issues with multiple PDs
Summary: Issues with multiple PDs
Status: RESOLVED FIXED
Alias: None
Product: PulseView
Classification: Unclassified
Component: Protocol decoding (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-23 22:53 CET by Uwe Hermann
Modified: 2018-04-20 17:21 CEST (History)
2 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Hermann 2017-03-23 22:53:59 CET
There seem to be some kind of issues when using multiple PDs in PulseView. Maybe only during live captures, maybe also with .sr files, needs to be checked.

How to reproduce:

 - Use some fx2lafw device, start PV, use 1Msamples + 1MHz samplerate, no triggers.

 - Put some kind of signal on e.g. D7 (some clock or whatever, doesn't really matter).

 - Add a timing PD, set it to use D7.

 - Add a pwm PD, set it to use D7 (choice of PD or channel likely doesn't matter).

 - Press Run in PV 20 times in a row, each time waiting a few seconds until the decode(s) must have finished.


Out of 20 times, only 6 times or so have decoded both PDs. The other 14 times only the first decoder will decode/display data, the other one will have the gray bars denoting "decode pending" or such.

It always seems to be the decoders other than the first one that are not getting run; the first one that was added will always run ok.

When using e.g. 4 different decoders, either the first one runs OK and the other 3 don't, or all 4 of them run OK. I haven't seen a case yet where only 3 ouf of 4 run or such.
Comment 1 Soeren Apel 2017-05-24 13:48:57 CEST
WONTFIX for now as I completely reworked pretty much all of the decoder handling code. Needs to be re-checked after those changes have been merged.
Comment 2 Soeren Apel 2017-07-23 21:14:03 CEST
Can you still reproduce this?
Comment 3 Uwe Hermann 2018-04-20 17:21:28 CEST
Did quite a bunch of tests with the method I described in the initial post, can't reproduce this with PV as of today indeed. This appears to have been resolved in the mean time. Closing the bug.

I did see one single issue during one of the >= 100 runs where one of the decoders yielded "Decoder reported an error", but I'm assuming that was unrelated and might be a bug in the PD itself or such.