Project

General

Profile

Bug #4171

Crash in epggrab

Added by Richard van der Hoff almost 8 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-01-10
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1-2405~geb495a0~wily
Affected Versions:

Description

tvheadend crashed with a segfault in epggrab this morning:

Jan 10 02:17:47 giles tvheadend[11902]: epggrab: grab done for 474.167MHz in Freeview (no data)
Jan 10 02:17:47 giles tvheadend[11902]: subscription: 1BCC: "epggrab" unsubscribing
Jan 10 02:17:47 giles tvheadend[11902]: mpegts: 474.167MHz in Freeview - close PID tables subscription [0042/0x7fa558004a80]
Jan 10 02:17:47 giles tvheadend[11902]: CRASH: Signal: 11 in PRG: /usr/bin/tvheadend (4.1-2405~geb495a0~wily) [70e798e391882a656623d3e286de1610b86d49b7] CWD: /
Jan 10 02:17:47 giles tvheadend[11902]: CRASH: Fault address 0x77656976656d (Address not mapped)
Jan 10 02:17:47 giles tvheadend[11902]: 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/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 /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 /usr/lib/x86_64-linux-gnu/libstdc++.so.6 /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libsystemd.so.0 /lib64/ld-linux-x86-64.so.2 /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/libgpg-error.so.0 /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 10 02:17:47 giles tvheadend[11902]: CRASH: Register dump [23]: 00007fa558002b70000000000000000000007fa558002b7000000000000003f800005616dcb35640000000000000004200007fa558004a80000000000000200100007fa55800000000000000ffffffff00007fa55800241000005616dcae5f60000077656976656500007fa558006601000000000000004000007fa563ffe39000005616d9c653b6000000000001020600000000000000330000000000000004000000000000000efffffffe7ffbba11000077656976656d
Jan 10 02:17:47 giles tvheadend[11902]: CRASH: STACKTRACE
Jan 10 02:17:47 giles tvheadend[11902]: CRASH: ??:0 0x5616d9bf95fd
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x7fa59277fd10
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c653b6
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c66257
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c68083
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c7189c
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9be3803
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9be0425
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9be17e9
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c7017f
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c86a05
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9c86ef5
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9bb56fd
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x5616d9bc0565
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: ??:0 0x7fa5927766aa
Jan 10 02:17:48 giles tvheadend[11902]: CRASH: clone+0x6d  (/lib/x86_64-linux-gnu/libc.so.6)

Files

bt.txt (4.38 KB) bt.txt backtrace from coredump Richard van der Hoff, 2017-01-10 11:04

History

#1

Updated by Richard van der Hoff almost 8 years ago

#2

Updated by Richard van der Hoff almost 8 years ago

This is happening every couple of days. Any idea what could be causing it?

#3

Updated by Jaroslav Kysela almost 8 years ago

Any chance to try to reproduce this issue with clang sanitizer? https://tvheadend.org/projects/tvheadend/wiki/Debugging#Memory-leaks-or-corruption

#4

Updated by Richard van der Hoff over 7 years ago

Hmph. It's been running fine ever since I switched to a sanitizer-enabled build, which might be because I upgraded my distro at the same time (long story).

I'll switch back to the stock build and see if it's stable now.

#5

Updated by Richard van der Hoff over 7 years ago

Continued experimentation seems to show that it reliably crashes when compiled without -fsanitize=address, and not when compiled with it :/

Also available in: Atom PDF