Bug #3537
Crash during sat>ip channel scan
0%
Description
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: Signal: 11 in PRG: tvheadend (4.0.8-3~gc870eb9~trusty) [910668c05a633357c9ee56aaf764295a04cf4c18] CWD: /
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: Fault address 0x2d0 (Address not mapped)
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: Loaded libraries: /lib/x86_64-linux-gnu/libssl.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libc.so.6 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libnss_compat.so.2 /lib/x86_64-linux-gnu/libnsl.so.1 /lib/x86_64-linux-gnu/libnss_nis.so.2 /lib/x86_64-linux-gnu/libnss_files.so.2
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: Register dump [23]: 000000000000000000007f64c4019f800000000000000000000000000000010000007f64caffc77000007f64c40193f0000000000000000000007f64caffc2a0000000000000000000007f64c40193f000007f64caffc4f000007f64c401936000000000000000010000000000000000000000000000000000007f64caffc1c00000000000483397000000000001020600000000000000330000000000000004000000000000000efffffffe7ffbba1300000000000002d0
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: STACKTRACE
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x43ef99
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x7f652445d340
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x483397
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x41b023
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x41b8ed
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x4814f4
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x4163cd
Jan 28 19:20:07 tv-server tvheadend1598: CRASH: ??:0 0x412fcf
Jan 28 19:20:07 tv-server kernel: [ 530.752262] tcp_server_star1734: segfault at 2d0 ip 0000000000483397 sp 00007f64caffc1c0 error 4 in tvheadend[400000+133000]
Jan 28 19:20:07 tv-server kernel: [ 530.754070] init: tvheadend main process (1598) killed by SEGV signal
Jan 28 19:20:07 tv-server kernel: [ 530.754082] init: tvheadend main process ended, respawning
Jan 28 19:20:07 tv-server tvheadend1755: main: Log started
Files
History
Updated by Richi Kane almost 9 years ago
Updated by - File 1kane-TVheadend.log 1kane-TVheadend.log added
I can confirm that bug. (just like https://tvheadend.org/issues/3235 and some more i guess)
Im using an DVB-C tuner and succesfully scanned and found all channels at the webInterface. I also set up the SAT>IP correct. Tuning/playing a channel with the client is working perfect (if u have the TuneData)
As Client i'm using DVBviewer and already noticed that Bug behavior: https://tvheadend.org/issues/2742 (client seems not/too late sending PLAY command) but not sure if that's the point here
Already tried newest unstable(seems to scan 2-3 freq before crash) and latest stable(seems to crash at 1st freq) but always crashes at SAT>IP scan.
attached full traceLog starting at the scanTrigger
Would be very nice if somebody could help! thank you
Updated by Richi Kane almost 9 years ago
after i read his report again i was just wondering about:
Stephan Ramel wrote at https://tvheadend.org/issues/3235:
... now i use version 4.1.632 and everything is fine. ...
so i just tried an older version (4.1-631~g7b05759) and hes right: it works fine! no crash! and successfull scan! i hope that could help to find that bug. thank you!
Updated by Jaroslav Kysela almost 9 years ago
Updated by Report the crash for the latest 4.1 code. The 4.0 won't be probably fixed.
Updated by Richi Kane almost 9 years ago
so should i create a new bug report for 4.1?
what version should i use for the new traceLog?
im not so familiar into compiling (also my hardware is kinda slow), thats why i could only use a provided debugPackage for that.
Updated by B C almost 9 years ago
Updated by always test with the latest code available. It should be fine to reporte here if it is the same issue.
Updated by Rüdiger Gubler over 8 years ago
Updated by Jaroslav Kysela wrote:
Report the crash for the latest 4.1 code. The 4.0 won't be probably fixed.
This means SAT>IP is currently not for production as 4.1 is marked as "use not for production"?!
Is there a stable release of the 4.1 code in the near future?
Updated by Jaroslav Kysela over 8 years ago
Rüdiger Gubler wrote:
Jaroslav Kysela wrote:
Report the crash for the latest 4.1 code. The 4.0 won't be probably fixed.
This means SAT>IP is currently not for production as 4.1 is marked as "use not for production"?!
Is there a stable release of the 4.1 code in the near future?
I'm going to release rc1 soon and already using the latest code in my home DVR system....
Updated by