2018-08-10, 18:58
The memory consumption (in the final "Accum" "Mem kB" column) looks fairly stable, peaking at about 216MB allocated from the start of monitoring (which may not all be allocated to kodi.bin, btw - it's for the whole system). From the log you posted it doesn't look like there is a problem.
If you leave bcmstat.sh running longer, does it show the figure in the final column progressively increasing (in a negative sense) over time? Any increase should be matched by a reduction of the kB figure in the "Memory Free/Used" column.
If the system is running out of memory then eventually the process that has consumed the most memory is usually killed by the out of memory process killer, and this is recorded in the system log (journalctl -a).
If you leave bcmstat.sh running longer, does it show the figure in the final column progressively increasing (in a negative sense) over time? Any increase should be matched by a reduction of the kB figure in the "Memory Free/Used" column.
If the system is running out of memory then eventually the process that has consumed the most memory is usually killed by the out of memory process killer, and this is recorded in the system log (journalctl -a).
