Bug #1188
Crash on subscribing to IPTV channel
0%
Description
This IPTV channel is fed from a Hauppauge HD PVR, streamed via VLC. It is an MPEG4 stream. It crashes tvheadend frequently, but the tvheadend process hangs and must be killed manually.
The problem is most frequent with this stream but an MPEG2 IPTV channel fed from a Hauppauge WinTV also occasionally crashes tvheadend.
Aug 31 16:52:05 videobox tvheadend[1873]: subscription: "192.168.1.108 [ XBMC Media Center ]" unsubscribing from "ASP2-Astro
"
Aug 31 16:52:05 videobox tvheadend[1873]: htsp: Got connection from 192.168.1.108
Aug 31 16:52:05 videobox tvheadend[1873]: htsp: 192.168.1.108: Welcomed client software: XBMC Media Center
Aug 31 16:52:05 videobox tvheadend[1873]: subscription: "192.168.1.108 [ XBMC Media Center ]" subscribing on "TRUE", weight:
150, adapter: "eth2", network: "<N/A>", mux: "239.255.12.11", provider: "<N/A>", service: "<N/A>", quality: 100
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: Signal: 11 in PRG: /usr/local/bin/tvheadend () [09e5e46cca3684773e291ca8fc7
579e0d2ad0e84] CWD: /
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: Fault address 0x7f8528804c28 (Address not mapped)
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: Loaded libraries: /lib/libssl.so.0.9.8 /lib/libcrypto.so.0.9.8 /lib/libz.so
.1 /usr/lib/libavahi-common.so.3 /usr/lib/libavahi-client.so.3 /lib/librt.so.1 /lib/libdl.so.2 /lib/libpthread.so.0 /lib/lib
c.so.6 /lib/libdbus-1.so.3 /lib64/ld-linux-x86-64.so.2 /lib/libnss_compat.so.2 /lib/libnsl.so.1 /lib/libnss_nis.so.2 /lib/li
bnss_files.so.2
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: Register dump [23]: 00000000fffffff9 00007f7de000ce10 0000000000000001 0000
00000000009e 00007f7dd8003020 0000000042e00100 0000000750801c00 0000000000000708 00007f7de57eabc0 0000000000000000 00007f7de
57eabc0 000000000134eae0 0000000000000001 000000010b800400 0000000000000000 00007f7de57eab60 000000000041b6b4 00000000000102
06 0000000000000033 0000000000000004 000000000000000e fffffffe7ffbfa17 00007f8528804c28
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: STACKTRACE
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/trap.c:139 0x424b2b
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: ??:0 0x7f7e08e98b40
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/parser_h264.c:388 0x41b6b4
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/parsers.c:1207 0x41b49e
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/parsers.c:339 0x419f70
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/tsdemux.c:121 0x41c732
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/tsdemux.c:255 0x41cb5e
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: /home/videobox/tvheadend-tvheadend-11f713d/src/iptv_input.c:116 0x4261cd
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: ??:0 0x7f7e08e90971
Aug 31 16:52:33 videobox tvheadend[1873]: CRASH: clone+0x6d (/lib/libc.so.6)
Aug 31 16:52:33 videobox kernel: [31062.385133] tvheadend[2382]: segfault at 7f8528804c28 ip 000000000041b6b4 sp 00007f7de57
eab60 error 4 in tvheadend[400000+85000]
History
Updated by Anonymous about 12 years ago
Here is an example of a crash when subscribing to the MPEG2 stream.
However we unsubscribed from the MPEG4 stream just prior, so it may still be caused by an issue with MPEG4.
Aug 26 15:50:47 videobox tvheadend[1929]: subscription: "192.168.1.103 [ XBMC Media Center ]" unsubscribing from "TRUE"
Aug 26 15:50:47 videobox tvheadend[1929]: subscription: "192.168.1.103 [ XBMC Media Center ]" subscribing on "AV-IN", weight: 150, adapter: "eth2", network: "<N/A>", mux: "239.255.12.15", provider: "<N/A>", service: "<N/A>", quality: 100
Aug 26 15:50:47 videobox tvheadend[1929]: CRASH: Signal: 11 in PRG: /usr/local/bin/tvheadend () [09e5e46cca3684773e291ca8fc7579e0d2ad0e84] CWD: /
Aug 26 15:50:47 videobox tvheadend[1929]: CRASH: Fault address (nil) (N/A)
Aug 26 15:50:47 videobox tvheadend[1929]: CRASH: Loaded libraries: /lib/libssl.so.0.9.8 /lib/libcrypto.so.0.9.8 /lib/libz.so.1 /usr/lib/libavahi-common.so.3 /usr/lib/libavahi-client.so.3 /lib/librt.so.1 /lib/libdl.so.2 /lib/libpthread.so.0 /lib/libc.so.6 /lib/libdbus-1.so.3 /lib64/ld-linux-x86-64.so.2 /lib/libnss_compat.so.2 /lib/libnsl.so.1 /lib/libnss_nis.so.2 /lib/libnss_files.so.2
Aug 26 15:50:47 videobox tvheadend[1929]: CRASH: Register dump [23]: 00007f9b4ce3fe40 00007f9b4ce3fe48 00007f9b4ce3fe90 0000000000000202 000000000126dea0 2056544350502030 00007f9b4ce3fe98 0000000001706910 00007f9b4ce3fe40 0000000000014bc0 0000000000010020 000000000126de80 2f6c617469676944 00000000012e7a10 0000000000000021 00007f9b48e3c2a0 00007f9b4cb377dd 0000000000010202 8b48000000000033 0000000000000000 000000000000000d fffffffe7ffbfa17 0000000000000000
Aug 26 15:50:47 videobox tvheadend[1929]: CRASH: STACKTRACE
Updated by Adam Sutton about 12 years ago
Updated by - Category set to IPTV
Have you tried this with the latest code? Not saying that will fix it, but it would be good to know whether its already been fixed.
Also you say MPEG4? presumably you mean H264 video in an MPEG2TS container? Just want to verify that.
Adam
Updated by Anonymous about 12 years ago
Adam Sutton wrote:
Have you tried this with the latest code? Not saying that will fix it, but it would be good to know whether its already been fixed.
Also you say MPEG4? presumably you mean H264 video in an MPEG2TS container? Just want to verify that.
Adam
We are using a very recent version, 2.99.28.g7d31b. Is this recent enough?
And you are correct, it is H.264 in MPEG2TS.
Tom
Updated by Adam Sutton about 12 years ago
2.99 anything is pretty old, though its fairly close to 3.0 I admit.
However since most development work (since the project mostly stopped) is since 3.0 I'd really appreciate if you could verify on git master before we continue the investigation.
Adam
Updated by Anonymous about 12 years ago
Adam Sutton wrote:
2.99 anything is pretty old, though its fairly close to 3.0 I admit.
However since most development work (since the project mostly stopped) is since 3.0 I'd really appreciate if you could verify on git master before we continue the investigation.
Adam
I didn't realise the version was out of date. I had a problem with git so I downloaded the zip - but ended up with an older revision.
I've now updated to the latest and it is running smoothly so far. Feel free to close this bug and if we run into the same issue, I will open a new one. Thanks.