Bug #5055

Live lock since parser changes

Added by Pablo R. 6 months ago. Updated 5 months ago.

Status:FixedStart date:2018-04-02
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Found in version:4.3-1213 Affected Versions:

Description

With newer versions since the changes of parsers I am receiving crashes (without getting to finish, they never get to show the crash lines) being tvheadend with the service running and totally frozen.

CRASH lines look as this:

Mar 28 12:46:02 Dell tvheadend[6277]: CRASH: Signal: 6 in PRG: /usr/bin/tvheadend (4.3-1213~g3ea69fe) [08f24e93094c6e9db45ca3942c4493d0feeb3bd8] CWD: /
Mar 28 12:46:02 Dell tvheadend[6277]: CRASH: Fault address 0x6f00001885 (N/A)
Mar 28 12:46:02 Dell tvheadend[6277]: CRASH: Loaded libraries: /usr/lib/x86_64-linux-gnu/libdvbcsa.so.1 /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/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 /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/libselinux.so.1 /lib/x86_64-linux-gnu/liblzma.so.5 /lib/x86_64-linux-gnu/libgcrypt.so.20 /lib/x86_64-linux-gnu/libpcre.so.3 /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-g

(crash lines end here) 

This always happens after approximately one day of interrupted usage.

gdb.txt Magnifier (305 KB) Pablo R., 2018-04-02 19:43

History

#1 Updated by Jaroslav Kysela 6 months ago

Could you provide again the full trace and also print the global lock before or after in the same gdb session: gdb command - 'print global_lock' .

#2 Updated by Pablo R. 6 months ago

I'm trying to get the deadlock again but I'm not capable with the latest version. It is very likely that this has already been solved.

P.D.: I do not have the previous crash lines, only the later ones that are the ones I have attached, that's why I was trying to reproduce it again.

#3 Updated by Pablo R. 5 months ago

Can be closed.

#4 Updated by Jaroslav Kysela 5 months ago

  • Status changed from New to Fixed

Also available in: Atom PDF