Bug #4217
Crash during multiple recordings
0%
Description
I'm running tvheadend in a docker container (image linuxserver/tvheadend) on a Synology NAS.
Tonight it was recording 2 or 3 shows simultaneously and showed this in the log:
2017-02-08 21:55:23.849 [ ALERT] CRASH: Signal: 11 in PRG: /usr/bin/tvheadend (4.1-2415~ge5f5a4278) [e2c33681d44e939c3ed86f1f39ef16594438bc5b] CWD: /var/run/s6/services/tvheadend
2017-02-08 21:55:23.849 [ ALERT] CRASH: Fault address 0 (N/A)
2017-02-08 21:55:23.849 [ ALERT] CRASH: Loaded libraries: /usr/bin/tvheadend /usr/lib/libhdhomerun.so /usr/lib/libdvben50221.so /usr/lib/libdvbapi.so /usr/lib/libucsi.so /lib/libssl.so.1.0.0 /lib/libcrypto.so.1.0.0 /lib/libz.so.1 /usr/lib/liburiparser.so.1 /usr/lib/libavfilter.so.6 /usr/lib/libavresample.so.3 /usr/lib/libavformat.so.57 /usr/lib/libavcodec.so.57 /usr/lib/libavutil.so.55 /usr/local/lib/libiconv.so.2 /lib/ld-musl-x86_64.so.1 /usr/lib/libswscale.so.4 /usr/lib/libpostproc.so.54 /usr/lib/libswresample.so.2 /usr/lib/libva.so.1 /usr/lib/librtmp.so.1 /usr/lib/libgnutls.so.30 /usr/lib/libbz2.so.1 /usr/lib/libxvidcore.so.4 /usr/lib/libx265.so.79 /usr/lib/libx264.so.148 /usr/lib/libvpx.so.3 /usr/lib/libvorbisenc.so.2 /usr/lib/libvorbis.so.0 /usr/lib/libtheoraenc.so.1 /usr/lib/libtheoradec.so.1 /usr/lib/libopus.so.0 /usr/lib/libmp3lame.so.0 /usr/lib/libva-drm.so.1 /usr/lib/libva-x11.so.1 /usr/lib/libX11.so.6 /lib/libssl.so.39 /lib/libcrypto.so.38 /usr/lib/libp11-kit.so.0 /usr/lib/libtasn1.so.6 /usr/lib/libnettle.so.6 /usr/lib/libhogweed
2017-02-08 21:55:23.849 [ ALERT] CRASH: Register dump [23]: 0000000000000018fefefefefefefeff00000000000000000000000000000206000000000000000100007f5f643c14a8000000000000000000007f5f69e9cf6000007f5f644b34dc000000000000000100007f5f643c1488000000000000000032c44a416c5a3d0a0000000000000000000000000000000000007f5f644b34d000007f5f6431769b000000000001020600000000000000330000000000000000000000000000000dfffffffc7ffbba110000000000000000
Nothing shows up before that and the application restarts.
Just wanted to ask if that may be a memory or docker container problem,
or if it is a tvheadend problem.
The other question is if the error message helps.
History
Updated by Jaroslav Kysela over 7 years ago
Updated by Could you retry with latest v4.1-2425-gcf818c0? There were some changes which might influence this issue.
Updated by hattori hanzo over 7 years ago
Updated by I tried yesterday but got the same error.
But I saw that after the crash, the docker process itself "docker daemon --ipv6=true" is at 100% CPU,
even though all containers are not doing any load and are still working fine.
So I assume that 4 or 5 SatIP Stream are too much for the docker network interface (although I use --net=host for multicast to work)?!
Anyway, I moved tvheadend to the main OS and everything seems to be running fine.
Sorry for the trouble 
Updated by