Description of problem: Just pressed the "Run" button. Version-Release number of selected component: pulseview-0.2.0-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: pulseview crash_function: Py_FatalError executable: /usr/bin/pulseview kernel: 3.17.2-200.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 Py_FatalError at /usr/src/debug/Python-3.3.2/Python/pythonrun.c:2372 #4 PyList_New at /usr/src/debug/Python-3.3.2/Objects/listobject.c:178 #5 PyEval_EvalFrameEx at /usr/src/debug/Python-3.3.2/Python/ceval.c:2239 #6 PyEval_EvalCodeEx at /usr/src/debug/Python-3.3.2/Python/ceval.c:3462 #7 function_call at /usr/src/debug/Python-3.3.2/Objects/funcobject.c:633 #8 PyObject_Call at /usr/src/debug/Python-3.3.2/Objects/abstract.c:2084 #9 method_call at /usr/src/debug/Python-3.3.2/Objects/classobject.c:323 #10 PyObject_Call at /usr/src/debug/Python-3.3.2/Objects/abstract.c:2084 #11 slot_tp_init at /usr/src/debug/Python-3.3.2/Objects/typeobject.c:5580 #12 type_call at /usr/src/debug/Python-3.3.2/Objects/typeobject.c:754
Created attachment 957853 [details] File: backtrace
Created attachment 957854 [details] File: cgroup
Created attachment 957855 [details] File: core_backtrace
Created attachment 957856 [details] File: dso_list
Created attachment 957857 [details] File: environ
Created attachment 957858 [details] File: limits
Created attachment 957859 [details] File: maps
Created attachment 957860 [details] File: open_fds
Created attachment 957861 [details] File: proc_pid_status
Created attachment 957862 [details] File: var_log_messages
Thanks for reporting this. Quick glance from the bactrace, I suspect the issue is with libsigrokdecode. Which device were you using as the data source, and which protocol decoder(s) did you have active?
(In reply to Alex G. from comment #11) > Thanks for reporting this. Quick glance from the bactrace, I suspect the > issue is with libsigrokdecode. I run the pulseview from bash console and when it crashed it printed out the following: $ pulseview Fatal Python error: GC object already tracked Current thread 0xb779b7c0: File "/usr/share/libsigrokdecode/decoders/uart/pd.py", line 341 in decode Aborted (core dumped) Today I also observed similar crash while changing the input channel using for RX for UART protocol decoder. $ pulseview Fatal Python error: GC object already tracked Current thread 0xb774e7c0: File "/usr/share/libsigrokdecode/decoders/uart/pd.py", line 367 in decode Aborted (core dumped) > > Which device were you using as the data source, and which protocol > decoder(s) did you have active? I'm using Saleae Logic Analyzer (8 channel): $ lsusb | grep Saleae Bus 003 Device 007: ID 0925:3881 Lakeview Research Saleae Logic I have connected 2 channels to RX and TX from the Arduino Mini Pro then press "Run" button (1MHz, 10M samples), and immediately uploaded the Sketch from Arduino IDE to the Arduino Min Pro board (it succeed). Then I added UART decoder and have tried to reproduce the scennario again but this time it crashed.
Let's see what the developers have to say about this. http://sigrok.org/bugzilla/show_bug.cgi?id=481
Is it possible to get an example .sr file that allows one to reproduce the issue?
(In reply to Alex G. from comment #14) I'm not sure if this would help, but AFAIR I didn't save any file as the program crashed. I've just used the scenario described in the comment #12 when the program crashed.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.