I posted to the issue page as well, and already got one reply. I am still wondering particularly about the Get() method big string theory.
Posts by w3techie
-
-
Sorry for my first suggestion. I was up late last night and not fully awake. Well, I guess that happened later. I was multitasking all day yesterday. Lol!
It seems as if the xbmc/GUIInfoLabel.cpp at master · xbmc/xbmc · GitHub : Get()) method is causing a too big string.
Also, I only mostly read this stuff at this stage, and rarely try it. So, I may not know anything. But nevertheless it never hurts to try. I used git and cloned the source and tested this particular file GUIInfoLabel.cpp, which I suspect is where the problem originates.
Here is what I have discovered. The includes are not on the right path.
As you can see the path for the GUIInfoLabel.h file is not the same as its location. It is looking for subfolders guilib/guiinfo/, but GUIInfoLabel.h is already inside the cwd.
Using nano to change the path of the GUIInfoLabel.h, I find the next file that it cannot locate is FileItem.h, and this is in the source directory xbmc/xbmc/. Using find to track down the rest of the files proves it is more than just a couple incorrect paths.find /src/xbmc/ -name FileItem.h
If you move this file it continues to prove an issue. I think perhaps this means you compiled it from source for one thing, and they do not realize the paths are not correct for another.So, I only wonder if that means I am correct and you compiled it from source? I wonder if it is a certain aspect of running the GUI that it is not capable of that way? What do you think?
Because if you did not compile it from source, when was the last time Kodi itself was updated. But wait, you are on LibreELEC which is read-only. So, no then I would wonder when was Kodi last updated? And when did the crashing began? Could it be at the same time?
I am only a tinkerer in this arena. I do not currently develop these things. I might give it a try though, and even fork Kodi. Most of my experience previously comes from web development, and embedded Linux is something I am trying to teach myself.
To answer the question of whether Kodi crashes on me. The answer is easily yes, but that is only because I am learning how to develop it and testing different server software on it. Sometimes I want to know what it takes to crash it on a device. Many times I think it is another piece of software has been installed and has a conflict. This is probably easier to do with multimedia apps.For instance, if you have your own build of FFmpeg installed. You must guard it from being replaced or compromised. In the end, I decide to compile all my multimedia from source. Kodi uses my own build of FFmpeg, which you can compile with Kodi by changing the path in xbmc/CMakeLists.txt at master · xbmc/xbmc · GitHub.
Scroll down to lines 50 to 60 and see where you can enter the path to FFmpeg. You can build FFmpeg with external codecs, and then build Kodi with FFmpeg. And if you insert your own advancedsettings.xml you are really rocking! If you build FFmpeg with Chromaprint, you can create autoexec.py and fetch metadata for music files from AcoustID. So, sorry for getting carried away with all the extra information. I rarely get to share it.
-
Did you ever find out what caused this?
I was wondering if you had tried using env_size to perhaps test the theory the string is too big. Or at least the theory that is causing the crash.Perhaps, in a manner like so?
kernel - What defines the maximum size for a command single argument? - Unix & Linux Stack ExchangeI am suggesting this because you are a capable embedded dev.