Kodi Community Forum

Full Version: Memory leak while playing video/stream
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello
I have a problem playing stream (.strm file, official internet service provider's stream udp://233.81.116.130:1234) and also video recorded from this stream (video and audio copy).
Kodi takes more and more RAM while playing and then OOM Killer closes kodi.bin process, then kodi restarts.

I have:
OS : ArchLinux
CPU : Celeron 440 2.0 ghz
MEM : 2GB RAM
VIDEO : Radeon 6450 (open-source drivers)
MB : MSI G31M3-L V2

I have made some research and here are the results:

Video AVC (PAL) ([email protected]) (CABAC 4 Ref Frames) Audio MP2 (stream and video file have these settings)
No hardware acceleration
No problem (Kodi and VLC, Radeon 6450)
VDPAU
Memory leak (Kodi, Radeon 6450)
No problem (VLC, Radeon 6450)
VAAPI
No problem (Kodi, Intel Core i5 laptop)

Also no problem with video and streams that have AVC L4.1 for example (another video settings than this video/stream) with VDPAU enabled in Kodi.
Only this stream/video and others with similar settings (AVC L3.0 and so on) have memory leak and have errors in debug log:
Code:
ERROR: ffmpeg[7F1425FC8700]: [h264] SPS unavailable in decode_picture_timing
ERROR: ffmpeg[7F1425FC8700]: [h264] non-existing PPS 0 referenced
ERROR: ffmpeg[7F1425FC8700]: [h264] SPS unavailable in decode_picture_timing
ERROR: ffmpeg[7F1425FC8700]: [h264] non-existing PPS 0 referenced
ERROR: ffmpeg[7F1425FC8700]: [h264] decode_slice_header error
ERROR: ffmpeg[7F1425FC8700]: [h264] no frame!

In Kodi 16.1 all was fine with this stream/video and others with similar settings (AVC L3.0 and so on).
Please help to solve this issue.
Thanks.

Stream:
JOURNALCTL(OOM).LOG
KODI_DEBUG_VH1_UDP_VDPAU.LOG
VDPAU_TRACE_VH1_VDPAU_UDP.LOG

Recorded video:
VH1_Clip_Mediainfo.log
VH1_Clip (Video AVC (PAL) ([email protected]) (CABAC 4 Ref Frames) Audio MP2).ts

Update (19 march 2017): Memory leak appeared after updating from Kodi 16.1 to Kodi 17. Maybe it was some error with settings, but changing "deinterlace" to OFF and then
revert back to Temporal solved the problem. For now there is no memory leak.