Bug #4835
TVHeadend crashes when the end of a recording is reached while fast-forwarding in Kodi
100%
Description
This is reproducible every time. The logged output from the crash is as follows. I have also attached the output of GDB "thread apply all bt full".
Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: Signal: 11 in PRG: /usr/bin/tvheadend (4.3-909~g50ab53f4e~bionic) [09425bd9a5956107c6cd2bfcd4517baae80bf754] CWD: / Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: Fault address 0x8000 (Address not mapped) Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: Loaded libraries: /usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 /usr/lib/x86_64-linux-gnu/libdvbcsa.so.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 /usr/lib/x86_64-linux-gnu/liburiparser.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/libavfilter.so.6 /usr/lib/x86_64-linux-gnu/libavformat.so.57 /usr/lib/x86_64-linux-gnu/libavcodec.so.57 /usr/lib/x86_64-linux-gnu/libavutil.so.55 /usr/lib/x86_64-linux-gnu/libva.so.2 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libsystemd.so.0 /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/libavresample.so.3 /usr/lib/x86_64-linux-gnu/libswscale.so.4 /usr/lib/x86_64-linux-gnu/libpostproc.so.54 /usr/lib/x86_64-linux-gnu/libswresa Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: Register dump [23]: 00000000000000000000000000000000000000000000000000000000000002060000000000000031000000000000003100005597d88c67c400007f87ec0015de00007f87ec0015de0000000000008000000000000000000400007f87ec017a20000000000000003100007f87ec0015de00005597d88c67e400007f88096ef11800007f8838e3ecc30000000000010283002b0000000000330000000000000004000000000000000efffffffe7ffbba130000000000008000 Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: STACKTRACE Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: /home/michael/Source/tvheadend/tvheadend-4.3/src/trap.c:148 0x5597d87cd87d 0x5597d862f000 Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: ??:0 0x7f883960eaf0 0x7f88395fc000 Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64 0x7f8838e3ecc3 0x7f8838cba000 Jan 7 10:17:44 mamarley-desktop tvheadend[5501]: CRASH: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 0x5597d87c7d8f 0x5597d862f000 Jan 7 10:17:45 mamarley-desktop tvheadend[5501]: CRASH: /home/michael/Source/tvheadend/tvheadend-4.3/src/htsmsg_binary.c:326 0x5597d87c7ff6 0x5597d862f000 Jan 7 10:17:45 mamarley-desktop tvheadend[5501]: CRASH: /home/michael/Source/tvheadend/tvheadend-4.3/src/htsp_server.c:3344 0x5597d87bbe37 0x5597d862f000 Jan 7 10:17:45 mamarley-desktop tvheadend[5501]: CRASH: /home/michael/Source/tvheadend/tvheadend-4.3/src/wrappers.c:181 0x5597d878f648 0x5597d862f000 Jan 7 10:17:45 mamarley-desktop tvheadend[5501]: CRASH: ??:0 0x7f8839603659 0x7f88395fc000 Jan 7 10:17:45 mamarley-desktop tvheadend[5501]: CRASH: clone+0x3f (/lib/x86_64-linux-gnu/libc.so.6) Jan 7 10:17:45 mamarley-desktop kernel: [154699.622593] tvh:htsp-write[5729]: segfault at 8000 ip 00007f8838e3ecc3 sp 00007f88096ef118 error 4 in libc-2.26.so[7f8838cba000+1dc000] Jan 7 10:17:45 mamarley-desktop systemd[1]: tvheadend.service: Main process exited, code=killed, status=11/SEGV Jan 7 10:17:45 mamarley-desktop systemd[1]: tvheadend.service: Failed with result 'signal'.
Files
Subtasks
History
Updated by Jaroslav Kysela almost 7 years ago
Updated by Michael Marley almost 7 years ago
- File valgrind.log valgrind.log added
When running under Valgrind, TVHeadend did not crash. Nevertheless, here is the output.
Updated by Michael Marley almost 7 years ago
I bisected. The offending commit is https://github.com/tvheadend/tvheadend/commit/4c3c047653effc546df19bbdf0252e115323c8a2.
Updated by Michael Marley almost 7 years ago
Is there anything else I can do or provide to help with getting this fixed?
Updated by Jaroslav Kysela almost 7 years ago
Provide another CRASH report. I changed a lot of code in latest days.
Updated by Michael Marley almost 7 years ago
I just tested with 4.3-941~gc34114f7e and I must have tried 9 or 10 different recordings, but I couldn't get it to crash either on startup or by fast-forwarding into the end. I guess one of the other changes you made must have fixed this.