Bug #4549

tvheadend_4.3-357~g3df769a8c crash

Added by Anonymous 3 months ago. Updated 3 months ago.

Status:FixedStart date:2017-08-24
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:General
Target version:-
Found in version:tvheadend_4.3-357~g3df769a8c Affected Versions:

Description

OS: Ubuntu 17.04 x64
Kernel: 4.10.0-32-generic

crash - log (4.26 KB) Anonymous, 2017-08-24 10:49

358-gdb.txt Magnifier (8.17 KB) Anonymous, 2017-08-25 07:40

History

#1 Updated by Mark Clarkstone 3 months ago

Have you installed the debug package too?

#3 Updated by Anonymous 3 months ago

v358: after record start.
(v334 was OK)

#4 Updated by Nihil Baxter 3 months ago

Same here. Sorry, not able to get some debug log now, but i think its the same problem. Platform is raspianjessie, every time recording starts server crashes.

#5 Updated by Jaroslav Kysela 3 months ago

Again, I need the trace with a binary which contains the debugging symbols. I don't see anything:

hread 1 "tvheadend" received signal SIGSEGV, Segmentation fault.
__strstr_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
40    ../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S: No such file or directory.
Already logging to gdb.txt.
#0  __strstr_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
No locals.
#1  0x0000558167a199fe in ?? ()
No symbol table info available.
#2  0x0000558167a14ffb in ?? ()
No symbol table info available.
#3  0x00005581679d6275 in ?? ()
No symbol table info available.
#4  0x0000558167a02bae in ?? ()
No symbol table info available.
#5  0x00005581679fd5df in ?? ()
No symbol table info available.
#6  0x0000558167972fe4 in ?? ()
No symbol table info available.
#7  0x00007fa18fe513f1 in __libc_start_main (main=0x5581679702b0, argc=6, argv=0x7fff244507d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff244507c8) at ../csu/libc-start.c:291
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 1342359027323378632, 94014277110880, 140733801891792, 0, 0, 5070380512001268680, 5107305685183634376}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7fff24450810, 0x7fa19386a168}, data = {prev = 0x0, cleanup = 0x0, canceltype = 608503824}}}
        not_first_call = <optimized out>
#8  0x0000558167974c8a in ?? ()
No symbol table info available.

See "No symbol table info available." .

#6 Updated by Anonymous 3 months ago

Sorry, my knowledge ends here.

#7 Updated by Mark Clarkstone 3 months ago

john - wrote:

Sorry, my knowledge ends here.

Did you install tvheadend-dbg? package & captured a new crash? You can install corekeeper to collect the dumps easier (they are placed in /var/crash).

#8 Updated by Anonymous 3 months ago

I'v installed gdb and ran tvh pid

#9 Updated by Mark Clarkstone 3 months ago

john - wrote:

I'v installed gdb and ran tvh pid

Ok, you need to install tvheadend-dbg, then restart the process & capture the gdb output again (from a fresh crash).

#10 Updated by Anonymous 3 months ago

From the log:

Starting program: /usr/bin/tvheadend -f -u hts -g video
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 1 (process 4533) exited normally]
No stack.
Quit

#11 Updated by Anonymous 3 months ago

I tried tvheadend_4.3-361~gaa2f92720, same bug..
Start record and tvh crashed.

#12 Updated by C K 3 months ago

Same here, i removed all files in ~/.hts/tvheadend/dvr/. Thats a dirty workaround (remember that you will loose all DVR meta data and auto records)

#13 Updated by Anonymous 3 months ago

Special.. tried and no crash anymore..

#14 Updated by Anonymous 3 months ago

363 seemed to be OK. With the old setup (VM)..

#15 Updated by Jaroslav Kysela 3 months ago

  • Status changed from New to Fixed

There's a fix in v4.3-363-ge1ad2342d for matroska muxer. Marking as resolved. Leave a note if it's not this case.

#16 Updated by Anonymous 3 months ago

Great, tnx!

Also available in: Atom PDF