Kodi Community Forum

Full Version: Memory Leak in KODI v18
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Greetings. I have started to notice a memory leak in KODI v18

/usr/lib/kodi/kodi.bin --version
18.2 Git:18.2-Leia Media Center Kodi

Hardware Specs:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

I came across a few discussions about memory leaks in the v18.2 RC and v19, but nothing about the 18.2 release.


top - 10:37:05 up 7 days, 16:18, 1 user, load average: 1.66, 0.52, 0.29
Tasks: 126 total, 1 running, 70 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2.0 us, 1.3 sy, 0.2 ni, 58.4 id, 38.0 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem : 56.9/3908132 [|||||||||||||||||||||||||||||||||||||||||| ]
KiB Swap: 0.0/0 [ ]
31722 root 20 0 2720152 1.046g 14572 S 5.5 28.1 1962:04 kodi.bin

I have been tracking memory utilization of the kodi.bin process, and it has increased almost 10x in less than a week.

Kodi.log (split in 2).
awukibunuj.kodi (paste)
ekaveqogag.kodi (paste)

Memory Utilization log (split in 2).
bipesizoyu (paste)
omugexipot (paste)
This was fixed in 18.3.
(2019-08-13, 17:41)smp1 Wrote: [ -> ]This was fixed in 18.3.

Awesome.  Thanks for the heads up.