Bug #3168
closedTvh crashes while scanning skyuk muxes
0%
Description
When trying to scan SkyUK muxes, tvhendend crashes on some muxes.
Mux like 11778000 V 27500000 2/3 are scanned without any problems.
But scanning 12324000 V 29500000 3/4 will unfortunately result in tvheadend crashes like this :
2015-10-17 21:39:36.034 [ DEBUG] mpegts: SkyUK - adding mux Multiplex [onid:0002 tsid:080F] in SkyUK to scan queue weight 5 flags 1000
2015-10-17 21:39:36.034 [ DEBUG] settings: saving to /root/.hts/tvheadend/input/dvb/networks/1704b992d2295e787797f037e5c59f9d/muxes/6825f65660b312ed90472cfca0b993e5/config
2015-10-17 21:39:40.009 [ DEBUG] nit: completed pid 16 table 00000000 / 00000000
2015-10-17 21:39:42.539 [ INFO] bouquet: new bouquet 'BSkyB Bouquet 14 - Interactive : Region 44'
2015-10-17 21:39:42.539 [ ALERT] CRASH: Signal: 11 in PRG: tvheadend (4.1-645~g46c82a8) [c042cab21121339b8635ed3c1c00c26db810a63d] CWD: /root
2015-10-17 21:39:42.539 [ ALERT] CRASH: Fault address (nil) (Address not mapped)
2015-10-17 21:39:42.539 [ ALERT] CRASH: Loaded libraries: linux-vdso.so.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
/lib/x86_64-linux-gnu/libz.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /usr/lib/x86_64-linux-gnu/libavcodec.so.56
/usr/lib/x86_64-linux-gnu/libavutil.so.54 /usr/lib/x86_64-linux-gnu/libavformat.so.56 /usr/lib/x86_64-linux-gnu/libswscale.so.3 /usr/lib/x86_64-linux-gnu/libavresample.so.2
/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 /usr/lib/x86_64-linux-gnu/libxvidcore.so.4 /usr/lib/x86_64-linux-gnu/libx264.so.142 /usr/lib/x86_64-linux-gnu/libvpx.so.1
/usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 /usr/lib/x86_64-linux-gnu/libvorbis.so.0 /usr/lib/x86_64-linux-gnu/libtheoraenc.so.1 /usr/lib/x86_64-linux-gnu/libtheoradec.so.1
/usr/lib/x86_64-linux-gnu/libspeex.so.1 /usr/lib/x86_
2015-10-17 21:39:42.539 [ ALERT] CRASH: Register dump [23]: 000000000000000000007f2c86ca09fa00007f2c86ff746000007f2c86db1d300000000000000001000000000000000100007f2c1803755000007f2c1803634000007f2c1804684000007f2c607df49
0000000000000001300007f2c18046840000000000000000000007f2c607df49a00007f2c86ceb5e000007f2c607df488000000000045cf80000000000001024600300000000000330000000000000004
000000000000000efffffffe7ffbba130000000000000000
2015-10-17 21:39:42.539 [ ALERT] CRASH: STACKTRACE
2015-10-17 21:39:42.554 [ ALERT] CRASH: /root/tvheadend/src/trap.c:148 0x442866
2015-10-17 21:39:42.559 [ ALERT] CRASH: ??:0 0x7f2c875168d0
2015-10-17 21:39:42.569 [ ALERT] CRASH: /root/tvheadend/src/bouquet.c:551 0x45cf80
2015-10-17 21:39:42.580 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/dvb_psi.c:110 0x4a58a3
2015-10-17 21:39:42.591 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/dvb_psi.c:668 0x4a7a52
2015-10-17 21:39:42.600 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/mpegts_table.c:105 0x4a21f2
2015-10-17 21:39:42.609 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/dvb_psi_lib.c:114 (discriminator 4) 0x49bced
2015-10-17 21:39:42.618 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/dvb_psi_lib.c:161 0x49bea1
2015-10-17 21:39:42.627 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/mpegts_input.c:1056 (discriminator 3) 0x496a08
2015-10-17 21:39:42.636 [ ALERT] CRASH: /root/tvheadend/src/input/mpegts/mpegts_input.c:1421 0x496b89
2015-10-17 21:39:42.642 [ ALERT] CRASH: /root/tvheadend/src/wrappers.c:177 0x416037
2015-10-17 21:39:42.646 [ ALERT] CRASH: ??:0 0x7f2c8750f0a4
2015-10-17 21:39:42.646 [ ALERT] CRASH: clone+0x6d (/lib/x86_64-linux-gnu/libc.so.6)
Segmentation fault
Result is the same using predefined muxes. And i don't use bouquet at all (looks like that might have something to do with the crash)
Related discussion : [[https://tvheadend.org/boards/5/topics/18158]]
Files
Updated by B C almost 10 years ago
I've seen this also yesterday during a complete scan on Astra 1, but did't pay much attention to it. It happend right after new Bouquet ARD....
Updated by Bo Byskov almost 10 years ago
Seems to be working fine now with the latest version.
Thank you.