Bug 1179 - PV seems to do unneeded operations after a decode aborted with an error
Summary: PV seems to do unneeded operations after a decode aborted with an error
Alias: None
Product: PulseView
Classification: Unclassified
Component: Other (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2018-04-24 19:48 CEST by Uwe Hermann
Modified: 2018-04-24 19:48 CEST (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Hermann 2018-04-24 19:48:17 CEST
How to reproduce:

 - Start PV, load dcf77_1800s.sr (and use libsigrokdecode commit 3f3c4614b, i.e. before the DCF77 PD bug was fixed which causes an error for dcf77_1800s.sr).
 - Add the DCF77 PD, let it run until it hits the error.

At this point PV should abort the decode and the feeding of further data into srd. This appears to be the case (no further "srd: Decoding: abs start sample 1131151360, abs end sample 1131413504 (262144 samples, 262144 bytes, unitsize = 1), instance dcf77-1." and similar messages in an -l 5 log.

However, something still seems to be going on, since after the PD error the CPU load is still relatively high for 10-20 seconds before it then goes to (near) zero. This is reproducible every time.

I'm assuming PV might still be doing *some* operations over the rest of the sample data (after the error) or something like that?