Continue to consume CPU even after Kodi terminates

[masnagam]

top when this issue occurs:

Mem: 926884K used, 74200K free, 844K shrd, 7624K buff, 562616K cached
CPU:   9% usr  54% sys   0% nic  32% idle   0% io   0% irq   2% sirq
Load average: 3.43 2.91 1.93 4/417 8166
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
 7848     8 root     R    57132   6%   2  25% /usr/local/sbin/minidlnad -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid -S
 7847     8 root     R    57132   6%   3  25% /usr/local/sbin/minidlnad -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid -S
    8     1 root     S    57132   6%   2   0% /usr/local/sbin/minidlnad -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid -S
 8153     0 root     S     1708   0%   1   0% sh
 8160  8153 root     R     1640   0%   0   0% top
    1     0 root     S     1632   0%   1   0% {run-minidlna} /bin/sh -eu /run-minidlna
 7996     1 root     S     1632   0%   1   0% sleep 300

top after several minutes (maybe, the end of the record reached):

Mem: 935880K used, 65204K free, 860K shrd, 8004K buff, 572696K cached
CPU:   9% usr   9% sys   0% nic  80% idle   0% io   0% irq   0% sirq
Load average: 0.92 1.63 1.69 2/421 8414
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
    8     1 root     S    57132   6%   1   0% /usr/local/sbin/minidlnad -f /etc/minidlna.conf -P /var/run/minidlna/minidlna.pid -S
 8401     0 root     S     1708   0%   0   0% sh
 8408  8401 root     R     1644   0%   1   0% top
    1     0 root     S     1632   0%   2   0% {run-minidlna} /bin/sh -eu /run-minidlna
 8394     1 root     S     1632   0%   2   0% sleep 300

docker logs that might be related to this issue:

upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1913: warn:  not found, responding ERROR 404
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1913: warn:  not found, responding ERROR 404
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnphttp.c:1959: info: Serving DetailID: 1643 [/mnt/nhk/607CF230.ニュース[字].m2ts]
upnpsoap.c:127: warn: UpdateObject Returning UPnPError 402: Invalid Args