Is entering an empty folder as slow, or does it scale with number of files?
Does it depend on the file type of files?
Note that archives (e.g. zip/rar) can cause a massive slowdown, as kodi will open and decompress to file if they contain video/subs etc.
Opening the same folder on LE 12.0.0 or 12.0.1: almost a minute
Can you check for any messages in the debug log during that minute?
Might be useful to install LE 11.0.6 and absolutely confirm that does not have the issue.
Just in case the issue is due to some change in the network or SMB server.
Hi, LibreElec 12.0.1 on a Rpi4, Synology NAS connected via SMB using 1Gbps ethernet. Fine for years, but somewhere around the 12.0.1 update (I can't say with certainty it was caused by it though)
You can always revert back to 12.0.0 and report if that works fine or has the issue.
If it really is due to 12.0.1 then the number is changes to consider is very much smaller than if it is 11->12.
It looks like from the log, the video that was playing when it crashes was using ffmpegdirect addon.
Do you get crashes when playing local content, or is it only videos using ffmpegdirect?
I'm not sure if ffmpegdirect causes significantly more memory usage.
A simple way to reduce some memory is to disable caching. In settings/services/Caching, set buffer mode to no buffer.
A lighter skin may be helpful.
So, it seems manageable for now, so thanks again. Hopefully the root issue will be resolved in further updates, just wanted to raise awareness of it.
Unfortunately this is just feature creep in kodi. Each version released tends to demand more memory.
A few releases back it was feasible to run kodi on a 512M pi, but that hasn't been possible for some time.
More recently, I'd say 2GB is needed for 4K kodi, and 1GB is okay for 1080p (*).
But it depends on the exact configuration. Using certain skins or add-ons may make even 1080p usage on 1GB unreliable.
(*) Note the workaround of "dtoverlay=cma,cma-384" will stop some 4k hevc content from being played, so isn't something that is going to be fixed. You make find "dtoverlay=cma,cma-320" is better for your situation.
Everything was unplugged during the RasPi switch, at least 30 Minutes.
Removing power from the TV (unplug from mains) is the important step here.
I'd power off avr too (although I think that is less likely to help).
From wiki:
LibreELEC 10.x also dropped support for Raspberry Pi Zero and other 512MB RAM devices as 1GB is now considered as the minimum RAM needed for a good Kodi experience.
.
Pi3A has 512M and is not supported. Pi3B has 1GB and is supported.
You could try LE 9.2.8 which may be somewhat usable (as long as you don't want the latest add-ons to work).
But it happens when i scan all the files. Now it doesn't happen when it is done.
Please be specific.
What happens when you scan all the files (crash? number of open files goes up?)
What doesn't happen? When what is done?
By scan all the files, do you mean using "Update library"?
If number of open files goes up while doing it, what is the highest number you see (and is it assigned to kodi.bin).
Does the number go down again?
The following command (run from ssh):
lsof | head -1 | awk '{ print "COUNT " $2 " " $1; }' && lsof +c 0 | awk '{ print $2 " " $1; }' | sort -rn | uniq -c | sort -rn | head -20will show which processes have files open. If there is a leak, then one process (possibly kodi.bin) is likely to be increasing regularly.
Do you see the numbers going up after a few minutes of kodi sitting idle?
Do you see the numbers going up after kodi playing a file and stopping?
There was a recent kernel fix that could be helpful here.
I think the fix is included in LE 12.0.1. Might be worth a test.
Thanks my friend. But when I play 4k remux, the libreleec outputs rgb. thats normal?
As I said
For 10-bit output at 4Kp60, it is necessary to output YCbCr 4:2:2, so we switch to that automatically.
At resolutions or refresh rates below that we will output the RGB directly.
The hdmi output varies on rgb 8bit to rgb 12bit depending on the media file (1080p sdr, 4k hdr etc).
I also have a amlogic box with coreelec, and is always displaying YCbCr 4:4:4, that is better?
No. As composition (e.g. combining subs or OSD items) happens in RGB space, there is no benefit in picture quality converting back to YCbCr before driving over hdmi.
For 10-bit output at 4Kp60, it is necessary to output YCbCr 4:2:2, so we switch to that automatically.
Some info from here:
$ grep -A9 HDMI-A-1 /sys/kernel/debug/dri/?/state
connector[33]: HDMI-A-1
crtc=crtc-2
self_refresh_aware=0
max_requested_bpc=8
colorspace=Default
broadcast_rgb=Automatic
is_limited_range=y
output_bpc=8
output_format=RGB
tmds_char_rate=74250000
$ kmsprint -p | grep -A 14 HDMI-A-1
Connector 0 (33) HDMI-A-1 (connected)
EDID (1) = blob-id 300 len 256 (immutable)
DPMS (2) = 0 (On) [On=0|Standby=1|Suspend=2|Off=3]
TILE (4) = blob-id 0 (immutable)
link-status (5) = 0 (Good) [Good=0|Bad=1]
non-desktop (6) = 0 [0 - 1] (immutable)
HDR_OUTPUT_METADATA (7) = blob-id 0
CRTC_ID (20) = object id 87
max bpc (34) = 8 [8 - 12]
left margin (35) = 0 [0 - 100]
right margin (36) = 0 [0 - 100]
top margin (37) = 0 [0 - 100]
bottom margin (38) = 0 [0 - 100]
Colorspace (39) = 0 (Default) [Default=0|SMPTE_170M_YCC=1|BT709_YCC=2|XVYCC_601=3|XVYCC_709=4|SYCC_601=5|opYCC_601=6|opRGB=7|BT2020_CYCC=8|BT2020_RGB=9|BT2020_YCC=10|DCI-P3_RGB_D65=11|DCI-P3_RGB_Theater=12]
Broadcast RGB (40) = 0 (Automatic) [Automatic=0|Full=1|Limited 16:235=2So alltogether I agree that it is a networking problem, but it seems to be caused by libreelec. Any ideas?
Start with the basics. run iperf (or iperf3) on your smb server. Run iperf/iperf3 on libreelec pi.
Check the speed.
iperf is in the Network Tools addon.
Looks like you are playing the file from a smb share?
To rule out a network issue, can you try playing the same file locally?
(e.g. copy it to sdcard or a usb drive and see if plays smoothly from there).
We are spending nearly half the time in KODI::RETRO::CDeltaPairMemoryStream::SubmitFrameInternal.
That seems to be used by the "rewind" feature. Disable it:
last week my system started to crash more or less often at different occasions. It just suddenly shows a square filled with rainbow colors for a second before it's restarting itself to the startscreen.
...System: LibreElec 12, Raspberry Pi 3 Model B Plus Rev 1.4, with 32 GB SD-card, Estuary Skin, USB dongle for remote control, and for a kind of power on/off button I connected a button to PIN 5+6 (GPIO3+GND) and added dtoverlay=gpio-shutdown to /flash/config.txt (after mount -o remount,rw /flash of course) and added autostart.sh and autostop.sh to .config. Can't think of anything else right now, but willing to provide anything needed.
The rainbow square shows you've had a reboot, rather than a crash.
That is actually pretty rare. It means something has intentionally requested a reboot or there has been a significant power failure.
I'd be suspicious of the power switch and gpio-shutdown overlay - can you remove those and see if there's any change?
