[bitstreamout]

The problem is back with Kodi Matrix 19.4 now with the new URL for JukeBox Radio 2 at https://maggie.torontocast.com:8076/flac.  After a while the sound does shutter ... I've tried to set

<cache>
                  <memorysize>139460608</memorysize>
                  <buffermode>1</buffermode>
                  <readfactor>20.0</readfactor>
</cache>

in advancedsettings.xml but this only inrease the time where it then happens again.  in the top of this QNAP system I see that the memory increases a lot causing the system to swap a lot

  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
4999  4989 admin    R    3756m199.5   0 49.9 /opt/Kodi19L/lib/kodi/kodi.bin

[bitstreamout]

The used PVR client is PVR IPTV Simple ... if I stop the channel replay the memory is freed ... but starting again one can see the increasing memory consumption and when the system becomes a swapping one the shutter is back

[bitstreamout]

Disabling of the spectrum vis makes no difference (beside CPU load) ... still increasing memory

[Dangelus]

@bitstreamout please use the edit feature to add more information to your existing post in the future please.

There is no need to keep adding tidbits of information in separate post every few minutes, it is untidy and doesn't make it easy for people to see what you are trying to say.

[emveepee]

First, thanks for letting me know JB Radio is back, I stopped listening last year when the went to aac. 

I don't think it is a PVR issue since I see what might be slow leak with a strm file  (PVR was no different) so you probably need to report a github issue with logs etc for a longer play.

CoreELECHK:~/music # free -s 10 -w | grep Mem
Mem:         3844000      468644     2985556       13828       83428      306372     3295992
Mem:         3844000      471620     2982580       13828       83428      306372     3293016
Mem:         3844000      474224     2979976       13828       83428      306372     3290412
Mem:         3844000      476588     2977612       13828       83428      306372     3288048
Mem:         3844000      479060     2975140       13828       83428      306372     3285576
Mem:         3844000      481540     2972660       13828       83428      306372     3283096
Mem:         3844000      483896     2970304       13828       83428      306372     3280740
Mem:         3844000      486580     2967620       13828       83428      306372     3278056
Mem:         3844000      488360     2965840       13828       83428      306372     3276276
Mem:         3844000      492560     2961640       13828       83428      306372     3272076
Mem:         3844000      490232     2963964       13828       83428      306376     3274400
Mem:         3844000      492140     2962056       13828       83428      306376     3272492
Mem:         3844000      505024     2949172       13828       83428      306376     3259608
Mem:         3844000      494452     2959744       13828       83428      306376     3270180
Mem:         3844000      495696     2958500       13828       83428      306376     3268936

Martin

[bitstreamout]

It takes a while to see the effect and much longer to hear the effect

              total        used        free      shared     buffers       cache   available
Mem:        1925252      937752       90900      361964      148528      748072      416168
Swap:      25060920      824784    24236136
Mem:        1925252      943520       99748      361968      144476      737508      410344
Swap:      25060920      824784    24236136
Mem:        1925252      947292      116436      361968      134392      727132      406624
Swap:      25060920      824784    24236136
Mem:        1925252      953968      120724      361968      129764      720796      399948
Swap:      25060920      824784    24236136
Mem:        1925252      959180      129172      361968      123776      713124      394736
Swap:      25060920      824784    24236136
[...]
Mem:        1925252     1002144      163584      378156       86644      672880      350396
Swap:      25060920      824784    24236136
Mem:        1925252     1025600      139780      382772       85524      674348      311700
Swap:      25060920      824784    24236136
Mem:        1925252     1007196      170132      382772       80064      667860      343324
Swap:      25060920      824784    24236136
[...]
Mem:        1925252     1037980      183516      370660       65916      637840      327628
Swap:      25060920      823248    24237672
Mem:        1925252     1073828      147816      370664       65916      637692      291852
Swap:      25060920      823248    24237672
Mem:        1925252     1072816      161388      370204       62068      628980      295396
Swap:      25060920      823248    24237672
[...]
Mem:        1925252     1157336      216536      373624        9468      541912      221632
Swap:      25060920      818384    24242536
Mem:        1925252     1307136       73624      374124        7044      537448       75024
Swap:      25060920      818896    24242024
Mem:        1925252     1201060      183264      374128        7036      533892      182880
Swap:      25060920      818896    24242024
[...]
Mem:        1925252     1302996      147856      372716        1956      472444      114916
Swap:      25060920      826848    24234072
Mem:        1925252     1203360      244068      376228        1916      475908      211064
Swap:      25060920      828392    24232528
Mem:        1925252     1147972      300176      371352        1780      475324      269260
Swap:      25060920      833012    24227908
[... shutter ...]
Mem:        1925252     1155484      270588      371516        1344      497836      250620
Swap:      25060920      882368    24178552
Mem:        1925252     1118580      293216      370500        1540      511916      280900
Swap:      25060920      889552    24171368

[emveepee]

Other than confirming what I noticed, this doesn't help so you still need to create the issue on github.

Martin

[bitstreamout]

https://github.com/xbmc/xbmc/issues/21526 ... let's see if I have forgotten something as last time I had reported an issue for kodi

[bitstreamout]

Seems no one cares about this report

[emveepee]

Technically that O/S version isn't supported so you can't expect too much, I'd try a report on mainstream linux.  Your post is also incomplete you didn't follow the instruction about the debug logs.

Martin

[bitstreamout]

AFAIK and AFAICS the containers used in QNAP OS for HD/Audio are all plain Ubuntu

[admin@dataslide ~]# chroot /share/CACHEDEV1_DATA/.qpkg/HD_Station/
root@dataslide:~# cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.04.6 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.6 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@dataslide:~# exit
[admin@dataslide ~]# uname -a
Linux dataslide 5.10.60-qnap #1 SMP Tue May 31 11:01:17 CST 2022 x86_64 GNU/Linux

[Klojum]

Seems no one cares about this report

Linux QNAP NAS HD-Station

So what does QNAP say on the matter? It's their version.

QNAP does their own tweaking, compiling and packaging of their Kodi releases.TeamKodi is not going to interfere there. We are not the free QNAP support forum.
Their version may be Ubuntu-based, but we here do not provide specific QNAP releases.

Also the various fragments of advancedsettings.xml settings and memory listings are insufficient.
There is also a CoreELEC reference, which may perhaps be better handle the memory thing at the CE forum itself?

[bitstreamout]

Now I've a log at https://paste.kodi.tv//edilikufim as well as new Linux based issue https://github.com/xbmc/xbmc/issues/21603

[bitstreamout]

This Kodi is the version of the QNAP community and has nothing todo with QNAP its self, see https://www.qnapclub.eu/en/qpkg/releasenotes/874 ... in other words it is a plain Kodi Matrix 19.4 compiled for the container OS Ubuntu 18.04.6 LTS

[emveepee]

Does turning off visualization make any difference? 

My point is community builds should really be supported by the QNAP community not Kodi Team, especially as you aren't running 19.5 another requisite for support.  Opening  a duplicate issue and calling it Ubuntu doesn't make it stock Ubuntu.

Martin