Can confirm that the memory leak is still present.
You might want to start by doing a clean installation without any of the banned repositories/addons https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons
If the problem persists post a new log, until then support for your setup is suspended.
so long,
Hias
I'm not seeing this here:
Time arm core Core Temp (Max) IRQ/s RX B/s TX B/s %user %nice %sys+ %total MemFreeKB / %used
======== ======= ======= =============== ====== =========== =========== ====== ====== ====== ====== =================
16:38:15 700Mhz 256Mhz 48.20C (48.20C) 613 189 371 1.99 0.00 0.62 2.98 3,653,008 / 5.5%
16:38:17 700Mhz 256Mhz 47.71C (48.20C) 619 32 126 1.99 0.12 0.50 2.96 3,653,008 / 5.5%
16:38:19 700Mhz 256Mhz 47.23C (48.20C) 634 32 126 1.99 0.12 0.74 2.95 3,653,008 / 5.5%
16:38:21 700Mhz 256Mhz 48.20C (48.20C) 645 32 126 2.23 0.12 0.62 2.95 3,653,008 / 5.5%
16:38:23 700Mhz 256Mhz 48.20C (48.20C) 608 32 126 2.11 0.12 0.50 2.96 3,653,008 / 5.5%
16:38:25 700Mhz 256Mhz 48.69C (48.69C) 610 32 126 1.99 0.12 0.37 2.94 3,653,008 / 5.5%
16:38:27 700Mhz 256Mhz 48.20C (48.69C) 629 32 126 2.23 0.25 0.37 2.96 3,653,008 / 5.5%
16:38:29 700Mhz 256Mhz 47.71C (48.69C) 654 94 126 2.11 0.12 0.37 3.08 3,653,008 / 5.5%
16:38:31 700Mhz 256Mhz 47.23C (48.69C) 622 139 126 2.11 0.25 0.50 2.95 3,653,008 / 5.5%
16:38:33 700Mhz 256Mhz 48.20C (48.69C) 616 246 126 2.11 0.12 0.50 2.83 3,653,008 / 5.5%
16:38:35 700Mhz 256Mhz 48.20C (48.69C) 1,408 3,773 2,854 2.73 0.12 1.49 4.69 3,653,028 / 5.5%
16:38:37 700Mhz 256Mhz 47.71C (48.69C) 628 32 126 1.99 0.25 0.37 2.96 3,653,028 / 5.5%
16:38:39 700Mhz 256Mhz 47.71C (48.69C) 656 233 876 2.23 0.25 0.25 3.08 3,653,028 / 5.5%
16:38:41 700Mhz 256Mhz 48.69C (48.69C) 581 65 158 2.11 0.12 0.37 2.82 3,653,028 / 5.5%
16:38:43 700Mhz 256Mhz 49.17C (49.17C) 651 32 126 1.99 0.12 0.62 3.07 3,653,280 / 5.5%
16:38:45 700Mhz 256Mhz 48.20C (49.17C) 654 183 313 2.23 0.12 0.50 2.96 3,653,280 / 5.5%
16:38:47 700Mhz 256Mhz 48.20C (49.17C) 634 32 126 2.23 0.12 0.50 2.94 3,653,028 / 5.5%
16:38:49 700Mhz 256Mhz 49.17C (49.17C) 576 32 126 2.11 0.25 0.12 2.95 3,653,028 / 5.5%
16:38:51 700Mhz 256Mhz 47.71C (49.17C) 638 32 126 2.11 0.12 0.50 2.94 3,653,028 / 5.5%
16:38:53 700Mhz 256Mhz 47.71C (49.17C) 638 32 126 2.11 0.12 0.50 3.08 3,653,028 / 5.5%
16:38:55 700Mhz 256Mhz 48.69C (49.17C) 641 32 126 2.23 0.25 0.50 2.85 3,653,028 / 5.5%
16:38:58 700Mhz 256Mhz 49.17C (49.17C) 585 32 126 2.11 0.12 0.25 2.94 3,653,028 / 5.5%
16:39:00 700Mhz 256Mhz 48.69C (49.17C) 647 63 126 2.23 0.12 0.62 3.10 3,653,028 / 5.5%
16:39:02 700Mhz 256Mhz 48.69C (49.17C) 715 364 456 2.23 0.12 0.74 3.08 3,653,028 / 5.5%
16:39:04 700Mhz 256Mhz 47.23C (49.17C) 647 32 126 2.11 0.12 0.50 2.97 3,653,028 / 5.5%
16:39:06 700Mhz 256Mhz 48.69C (49.17C) 576 62 146 2.11 0.12 0.50 2.96 3,653,028 / 5.5%
16:39:08 700Mhz 256Mhz 47.71C (49.17C) 640 32 126 1.86 0.12 0.62 2.95 3,653,028 / 5.5%
16:39:10 700Mhz 256Mhz 49.66C (49.66C) 646 32 126 2.23 0.12 0.37 2.96 3,653,028 / 5.5%
16:39:12 700Mhz 256Mhz 48.20C (49.66C) 648 32 126 2.11 0.12 0.87 2.95 3,653,028 / 5.5%^CWhat were you (or kodi doing) at that time?
so long,
Hias
Whatever. You have your theory and I tried to explain some more details. Anyways I'm out of this thread.
so long,
Hias
Under the hood JACK is using ALSA (as that's the only way to access audio devices in Linux). So adding JACK to the chain is at best a workaround for some kodi bug.
so long,
Hias
If kodi is crashing on other Linux systems, too, then it'd be best to report it to kodi devs here: https://github.com/xbmc/xbmc/issues - this sounds like it might be a kodi bug.
so long,
Hias
Do you have the AVR connected to SPDIF out on the TV?
The log looks fine, kodi is properly signalling PCM and passthrough to the hdmi driver.
So this likely is an issue with your TV's SPDIF out, AVR's SPDIF in or some combination of both. Check if your TV has some settings to control SPDIF out.
so long,
Hias
Do a clean install without your piracy crap addons - that stuff is not supported here.
so long,
Hias
Thanks for testing, I've PR'ed the workaround/fix https://github.com/LibreELEC/LibreELEC.tv/pull/8126
Concerning your other SPDIF/passthrough issue: please open a separate bug report thread for that and provide a full debug log (using pastekodi or the log file upload function in LE settings)
so long,
Hias
hbbs can you please test and report back if this build works?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi2.arm-12.0-devel-20230908210215-01c68ef.tar
so long,
Hias
hbbs thanks, I've managed to reproduce this issue locally now and will investigate it. ATM we don't need anything else from you
so long,
Hias
Thanks a lot for reporting back, the fix for RPi, Allwinner, Rockchip etc has already been added to LE11 and LE12 https://github.com/LibreELEC/LibreELEC.tv/pull/8123 and will be in the next nightly builds (and also in further releases): https://test.libreelec.tv/
Amlogic is a different thing though, the LE kernels didn't include the offending change (but other changes that might affect multichannel PCM), I'll leave that to chewitt
so long,
Hias
Thanks, kodi_crashlog_20230905155633.log indeed shows that kodi is crashing in the alsa lib, I've informed heitbaum about it.
so long,
Hias
Hmm, unfortunately the interesting bit, the stack backtrace, was missing in the log.
Could check if you have more kodi_crashlog files in /storage/.kodi/temp and upload them, too (eg with "pastebinit
/storage/.kodi/temp/kodi_crashlog_<SOMETIMESTAMP>.log")
According to the log there should also be a /storage/.kodi/temp/kodi_crashlog_20230907190747.log file (there might be more, but older ones will eventually get cleaned up automatically).
so long,
Hias
My bet would be on the ALSA update https://github.com/LibreELEC/LibreELEC.tv/pull/8095
But we need logs to be certain:
Add "ssh" to the end of cmdline.txt (on the same line, use eg notepad++ on windows to edit that on the FAT partition), then quickly ssh in after boot, while kodi is in a crash loop and enter "systemctl stop kodi".
Then run "pastecrash" to update the crash log info and post the URL you got - from there we can look further.
so long,
Hias
Can you please test with this LE11 RPi4 build and report back if multichannel PCM works again?
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20230907220746-677274a.tar
so long,
Hias
Did it work fine with 11.0.1?
If yes then quite certainly the reason is I messed up (chewitt reported it to me earlier this week). A fix for that should be out soon (just need to find some spare time).
so long,
Hias
I've had good experience with Sandisk Extreme Pro 32GB, just be sure to buy from a reputable seller as there are lots of fakes out there from shady sellers on ebay, aliexpress, amazon marketplace etc.
Anything below 32GB doesn't make sense price-wise, if you need more space then choose a larger one (although I'd use a separate, external USB storage device for that).
so long,
Hias
We are still waiting for an updated rpi.gpio package which finally uses the standard libgpiod method instead of the ancient, hacky direct memory access which is soon going to break.
Once that's released we'll update the package and the RPi tools addon and make it available for RPi4/aarch64 as well.
so long,
Hias