Bug 901 - Crash when capture data and activating NEC-IR protocol
Summary: Crash when capture data and activating NEC-IR protocol
Status: RESOLVED DUPLICATE of bug 876
Alias: None
Product: PulseView
Classification: Unclassified
Component: Protocol decoding (show other bugs)
Version: 0.3.0
Hardware: x86 Windows
: Normal major
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-26 19:06 CET by Fred E
Modified: 2017-03-01 10:54 CET (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred E 2017-02-26 19:06:24 CET
Hi
Just installed sigrok on 26/2/2017. Windows 10 up-to-date machine.
When capturing IR data, application works fine.
When I add NEC-IR protocol filter, it starts to capture, I can see my 4 pulse of capturing, timeline continues, then crash. On the screen, feels like Nothing is displayed (so decoded) on the protocol analizer line, maybe analysis take place at the end of the capture.

Without connecting protocol decoder on channel 0 it works great.
Tested several options and have 100% of crash.

I am not Sigrok expert, so don't know how to trace, or download.

Let me know and I will provide more détails. 

Is there a way to capture, save and then decode after capture to split the process ?

Regards.
Comment 1 Uwe Hermann 2017-02-26 20:15:56 CET
Hi, please try the latest Windows installer (it got rebuilt 20 minutes ago with some fixes that might help).

The issue might be fixed for you, at least for the first run. With multiple runs there might still be some problems (see bug #902), please let us know if you're running into issues there as well.

(this is very likely unrelated to te specific decoder, it could happen with any of them)

"Is there a way to capture, save and then decode after capture to split the process"

---> Yes, just capture then click "Save as" in PulseView to save to an *.sr file.
Comment 2 Uwe Hermann 2017-03-01 10:54:06 CET
I've been contacted by Fred E via PM, he said the issue is resolved now, so it's very likely this has been a duplicate of bug #876, marking as such.

*** This bug has been marked as a duplicate of bug 876 ***