2023-02-23, 18:46
@Lunatixz — indeed, as you say. From my previous email:
As to the issue related to the contentpanelslide, aye, if you're not using the animation, it should be removed. It's just a warning, sure, and has no direct impact on Kodi. However, as you can see from the posted logs, it is followed by an error. As said, I'm not really familiar with the whole Kodi ecosystem, but my best guess is that the failure to load the contentpanelslide has, as a consequence, some sort of small window/panel/element associated with it that cannot get the focus (possibly because it hasn't been correctly instantiated). Does that make a difference and/or an impact on Kodi? My guess is that it doesn't, but... there is a reason why Kodi flags it as an error as opposed to merely a warning. Just because you cannot see any difference, it does not mean that there isn't any impact; for example, Kodi might allocate some sort of memory buffer in advance, expecting that it will be instantiated correctly at some point. When this doesn't happen (due to lack of the animation panel thingy), 'something' is not working as it should, and, who knows, perhaps that memory buffer is never reclaimed by the system — meaning that every time the screensaver launches, a tiny little bit of memory never gets released back to the system; and, over time, that tiny little bit grows and grows, until eventually Kodi crashes.
Mind you, that is only speculation, of course. Because I use an underpowered Raspberri Pi Zero 2 W with only 512 MB of on-chip RAM, I see those kinds of memory-running-low-crashes much earlier than a 'normal' system with several GBytes of RAM to spare :-)
BTW, the reason I picked your screensaver by default is because it is available from the official Kodi repository, and, as such, a much more trustworthy source :-) There are other similar screensavers for Kodi elsewhere; I tested out Mark König's Bing Pictures Screensaver, which, however, only has a 19.X version available from the non-official kodinerds.net repo. It works flawlessly, so you might take a look at the relevant bits of code he used. It's not exactly a copy of yours, mind you; it lacks some features (such as a smoother transition) while adding some others (like pasting the current time in very big letters over the image). Nevertheless, it doesn't post any warnings or errors, and the Bing caption for the picture does work — and is even printed in the correct language. I'm sure it's worth taking a look at it
(I did!)
Cheers and thanks for all your work & efforts!
- Screen shows "info" instead of the name of the pictures currently being viewed
- Warning on the logs for "Skin has invalid include: contentpanelslide", followed by "ERROR <general>: Control 101 in window 13000 has been asked to focus, but it can't"
As to the issue related to the contentpanelslide, aye, if you're not using the animation, it should be removed. It's just a warning, sure, and has no direct impact on Kodi. However, as you can see from the posted logs, it is followed by an error. As said, I'm not really familiar with the whole Kodi ecosystem, but my best guess is that the failure to load the contentpanelslide has, as a consequence, some sort of small window/panel/element associated with it that cannot get the focus (possibly because it hasn't been correctly instantiated). Does that make a difference and/or an impact on Kodi? My guess is that it doesn't, but... there is a reason why Kodi flags it as an error as opposed to merely a warning. Just because you cannot see any difference, it does not mean that there isn't any impact; for example, Kodi might allocate some sort of memory buffer in advance, expecting that it will be instantiated correctly at some point. When this doesn't happen (due to lack of the animation panel thingy), 'something' is not working as it should, and, who knows, perhaps that memory buffer is never reclaimed by the system — meaning that every time the screensaver launches, a tiny little bit of memory never gets released back to the system; and, over time, that tiny little bit grows and grows, until eventually Kodi crashes.
Mind you, that is only speculation, of course. Because I use an underpowered Raspberri Pi Zero 2 W with only 512 MB of on-chip RAM, I see those kinds of memory-running-low-crashes much earlier than a 'normal' system with several GBytes of RAM to spare :-)
BTW, the reason I picked your screensaver by default is because it is available from the official Kodi repository, and, as such, a much more trustworthy source :-) There are other similar screensavers for Kodi elsewhere; I tested out Mark König's Bing Pictures Screensaver, which, however, only has a 19.X version available from the non-official kodinerds.net repo. It works flawlessly, so you might take a look at the relevant bits of code he used. It's not exactly a copy of yours, mind you; it lacks some features (such as a smoother transition) while adding some others (like pasting the current time in very big letters over the image). Nevertheless, it doesn't post any warnings or errors, and the Bing caption for the picture does work — and is even printed in the correct language. I'm sure it's worth taking a look at it
(I did!)Cheers and thanks for all your work & efforts!
