Running Kodi 18.4 on an Intel NUC, everything appears to be working fine, but I've noticed in the kodi.log file that it is littered with Notice messages from GL:
2020-07-01 21:57:36.740 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.757 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.758 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.758 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.767 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.768 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.768 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.775 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.775 T:140161295145088 NOTICE: GL: NPOT texture support detected
I have all debug logging disabled, component-specific logging disabled, and event logging disabled, but these messages still keep filling up the log file.
Is there a way to stop these messages from filling the log file? Or is this an indication of a problem that I actually need to fix?
Edit: I've since updated to Kodi 18.7, and still seeing the same messages over and over in the log.
Edit 2: I've now discovered these log messages start appearing whenever I am watching Live TV and have the Program Guide up - Live TV shows in the bottom left corner in a small window, and I guess this is what is creating all of these messages.
(2020-07-18, 00:04)dapharsyde Wrote: [ -> ]Running Kodi 18.4 on an Intel NUC, everything appears to be working fine, but I've noticed in the kodi.log file that it is littered with Notice messages from GL:
2020-07-01 21:57:36.740 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.744 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.757 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.758 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.758 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.767 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.768 T:140161295145088 NOTICE: GL: NPOT texture support detected
2020-07-01 21:57:36.768 T:140161295145088 NOTICE: GL: Using GL_ARB_pixel_buffer_object
2020-07-01 21:57:36.775 T:140161295145088 NOTICE: GL: Selecting YUV 2 RGB shader
2020-07-01 21:57:36.775 T:140161295145088 NOTICE: GL: NPOT texture support detected
I have all debug logging disabled, component-specific logging disabled, and event logging disabled, but these messages still keep filling up the log file.
Is there a way to stop these messages from filling the log file? Or is this an indication of a problem that I actually need to fix?
Edit: I've since updated to Kodi 18.7, and still seeing the same messages over and over in the log.
Edit 2: I've now discovered these log messages start appearing whenever I am watching Live TV and have the Program Guide up - Live TV shows in the bottom left corner in a small window, and I guess this is what is creating all of these messages.
Another thing I don't understand is where the message "GL: NPOT texture support detected" is coming from. This looks to be a string from xbmc krypton's version of the file: xbmc/cores/VideoPlayer/VideoRenderers/LinuxRendererGLES.cpp
For example, searching github for this string only turned up repos from 2018 or earlier, like this one -
https://github.com/rusguliev/xbmc-17Kryp...erGLES.cpp
I just updated to Leia (18.7.1) using the libreelec release at
http://releases.libreelec.tv/LibreELEC-G...2.3.img.gz - so how am I getting debug messages from what appears to be Kodi 17's Video Player?
Why don't you provide the full
debug log (wiki) via a pastebin website instead of one puzzle piece, so people can have a proper look.
(2020-07-18, 14:07)Klojum Wrote: [ -> ]Why don't you provide the full debug log (wiki) via a pastebin website instead of one puzzle piece, so people can have a proper look.
Sure thing - here is the debug log with debugging disabled, but still shows these NOTICE messages littering the log file whenever I have the program guide up -
http://paste.kodi.tv/udedamipac
And here is the debug log with debugging enabled - since the file is 2.2MB, it could not be uploaded to pastebin, so here it is from filebin -
https://filebin.net/zg2zsr5c3u9lpimw
In both tests, the steps to replicate the issue were the same:
1. Wait for Kodi to boot
2. Open Live TV -> Guide -> Choose a channel -> Switch to Channel
3. Press 'e' to show Program Guide/EPG - This step is what causes the GL: NOTICE messages to start appearing in the log
Again, what I find most unusual is that the message string "NPOT texture support detected" hasn't been around since Kodi 17 Krypton.
Please remove emby and post the log again.
No one can help you with debugging disabled.
Quote:2020-07-18 14:06:44.986 T:140580881651840 DEBUG: ------ Window Deinit (VideoFullScreen.xml) ------
2020-07-18 14:06:44.993 T:140580881651840 DEBUG: ------ Window Init (MyPVRGuide.xml) ------
Quote:2020-07-18 14:06:38.087 T:140577291101952 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.TypeError'>
Error Contents: an integer is required
Traceback (most recent call last):
File "/storage/.kodi/userdata/addon_data/plugin.video.emby/emby/objects/player.py", line 97, in onAVStarted
item = self.set_item(current_file, False)
File "/storage/.kodi/addons/plugin.video.emby/resources/lib/hooks/player.py", line 271, in set_item
self.playlist = xbmc.PlayList(self.monitor.playlistid)
TypeError: an integer is required
Something seems to constantly cause a render reconfigure. As there are many errors in your log (mythtv, emby and others).
Backup your .kodi folder, afterwards remove it enitrely and start with a simple file, without emby, without having myth enabled.
Issue gone?
(2020-07-19, 08:28)fritsch Wrote: [ -> ]Please remove emby and post the log again. No one can help you with debugging disabled.
Quote:2020-07-18 14:06:44.986 T:140580881651840 DEBUG: ------ Window Deinit (VideoFullScreen.xml) ------
2020-07-18 14:06:44.993 T:140580881651840 DEBUG: ------ Window Init (MyPVRGuide.xml) ------
Quote:2020-07-18 14:06:38.087 T:140577291101952 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.TypeError'>
Error Contents: an integer is required
Traceback (most recent call last):
File "/storage/.kodi/userdata/addon_data/plugin.video.emby/emby/objects/player.py", line 97, in onAVStarted
item = self.set_item(current_file, False)
File "/storage/.kodi/addons/plugin.video.emby/resources/lib/hooks/player.py", line 271, in set_item
self.playlist = xbmc.PlayList(self.monitor.playlistid)
TypeError: an integer is required
Something seems to constantly cause a render reconfigure. As there are many errors in your log (mythtv, emby and others).
Backup your .kodi folder, afterwards remove it enitrely and start with a simple file, without emby, without having myth enabled.
Issue gone?
Here is a cleaner debug log, with only the pvr.mythv addon and estuary mod v2 skin -
https://paste.kodi.tv/xifosajoci
This skin happens to be one that shows live tv in the bottom left corner in a small window while the epg is up:
While this video is playing in the corner, the GL: NOTICE messages are generated in the log file. I assume this is what is causing the "render configure" you mentioned.
Yes. Thought to be honest - I don't know why :-)