Starting with a fresh profile solved this issue. Guess something broke by too much playing around with skins for to get my custom home menu entries correct.
I'll keep an eye on it.
Starting with a fresh profile solved this issue. Guess something broke by too much playing around with skins for to get my custom home menu entries correct.
I'll keep an eye on it.
Play a movie, forward to 30 minutes (for to have it set a resume point) and stop the movie.
All other devices send the "mysql execute" but LE.
It shows the missing executes, but I'll provide more.
Hi there.
I'm running a central MySQL DB with multiple clients. All clients are Kodi 18.5. All clients save the resume points if watching a video:
Laptop (Bionic): (tail -f kodi.log | grep -i mysql)
2019-12-05 09:46:50.895 T:140293067859712 DEBUG: Mysql execute: DELETE FROM settings WHERE idFile=74502019-12-05 09:46:50.910 T:140293067859712 DEBUG: Mysql execute: update files set playCount=NULL,lastPlayed='2019-12-05 09:46:50' where idFile=74502019-12-05 09:46:50.919 T:140293067859712 DEBUG: Mysql execute: insert into bookmark (idBookmark, idFile, timeInSeconds, totalTimeInSeconds, thumbNailImage, player, playerState, type) values(NULL,7450,1809.793130,7001.630000,'','VideoPlayer','', 1)
This is Amlogic Box running Coreelec:
2019-12-05 09:25:00.400 T:3610657664 DEBUG: Mysql execute: DELETE FROM settings WHERE idFile=74502019-12-05 09:25:00.422 T:3766551424 DEBUG: Mysql execute: update files set playCount=NULL,lastPlayed='2019-12-05 09:25:00' where idFile=7450
2019-12-05 09:25:00.431 T:3766551424 DEBUG: Mysql execute: insert into bookmark (idBookmark, idFile, timeInSeconds, totalTimeInSeconds, thumbNailImage, player, playerState, type) values(NULL,7450,3055.282872,7001.630000,'','VideoPlayer','', 1)
This is Libreelec (9.2.0) (Rpi3):
2019-12-05 09:51:11.188 T:1793299328 DEBUG: Mysql execute: DELETE FROM settings WHERE idFile=7448
As you can see, all systems (except LE) do execute the insert into the Mysql DB!?
# grep -i mysql .kodi/temp/kodi.log <type>mysql</type>
<type>mysql</type>
2019-12-05 09:35:16.603 T:1807721344 NOTICE: MYSQL: Connected to version 10.4.10-MariaDB-1:10.4.10+maria~bionic-log
2019-12-05 09:35:26.481 T:1648538496 NOTICE: [plugin.video.mediathekview-0.6.2:Updater]: Database driver: External (mysql)
2019-12-05 09:35:26.481 T:1648538496 NOTICE: [plugin.video.mediathekview-0.6.2:StoreMySQL]: Using MySQL connector version 1.1.7
2019-12-05 09:35:26.695 T:1648538496 NOTICE: [plugin.video.mediathekview-0.6.2:StoreMySQL]: Connected to server 192.168.5.13 running 10.4.10-MariaDB-1:10.4.10+maria~bionic-log
2019-12-05 09:38:01.949 T:1249416064 DEBUG: Mysql execute: DELETE FROM settings WHERE idFile=7448
2019-12-05 09:51:11.188 T:1793299328 DEBUG: Mysql execute: DELETE FROM settings WHERE idFile=7448
As you can see, the connection is established, no errors regarding MySQL and even Mediathekview is able to connect to the DB.
Only thing is, there's no bookmark execution running into the DB if a video is played from LE.
I noticed that even playcounts for audio aren't saved into the DB from LE, but I have no logs available atm.
I'm running kszaq's 8.4.3.1 latest S905X release. May I ask how 'testy' the testing version for S905X is?
Burn a new SD card. Possibly that's also why you're getting errors from YouTube.
Clean install did it! Sadly I had no backup
Hi. I'm having problems with YouTube addon. It stopped working and is throwing Errors in log cause of SSLError. Anyone with similar problems?
And a second problem:
I seem to have corruptions on my filesystem
What's the best way to do a clean install?
Can't see a memleak, but a segfault together with a different platform. What tells you it's a memleak?
No, sadly no real solution. As from the tests we did, best is to not have any addon querying the db (like Library Data Provider).
Dave did some changes which are added in kodi 17.1.
Have you've got a little more info on your setup?
Ok, we've found the cause. It's not LE and Rpi only, but platform independent! Dave's working on a solution
Pls, couldn't anyone tell what's needed to get this one pinned down?
Dave and me are down to it being caused by Library Data Provider and/or Skin.Widget (both coming along with Xonfluence) and the regular queries done by that addons to the DB. MyMusic DB (MariaDB) is quite large 120k songs...
Have had problems with mysql, so I switched to MariaDB as it's alot faster!
Latest Milhouse (#0305) is better in the matter of "leaking" (not that fast as in the video), but there are still crashes (see above)
I'm checking against Estuary with LDP & S.W running to see if it has an influence.
No problem running Xonfluence with LDP & S.W on Linux (14.04) or Amlogic (kszaq) against my DB, only RPi3!
This is Milhouse #303 running since yesterday evening.
LDP & skin.widget together with Xonfluence (tricked it into with adapting xbmc.gui version from required 5.12 to 5.13).
This was running over night and produced 9 crashlogs and at least 1 reboot :s
# grep -C6 "Thread debugging using libthread_db enabled" kodi_crash*
kodi_crash.log:[Thread debugging using libthread_db enabled]
kodi_crash.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crash.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crash.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crash.log-#0 0x76f98b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crash.log-[Current thread is 1 (Thread 0x74f2a000 (LWP 2304))]
kodi_crash.log-
--
kodi_crashlog_20170305224525.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170305224525.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170305224525.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170305224525.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170305224525.log-#0 0x008daf48 in CMusicDatabase::SetMusicTagScanVersion(int) ()
kodi_crashlog_20170305224525.log-[Current thread is 1 (Thread 0x74f10000 (LWP 453))]
kodi_crashlog_20170305224525.log-
--
kodi_crashlog_20170306002511.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306002511.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306002511.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306002511.log-Program terminated with signal SIGABRT, Aborted.
kodi_crashlog_20170306002511.log-#0 __GI_raise ([email protected]=6) at ../sysdeps/unix/sysv/linux/raise.c:58
kodi_crashlog_20170306002511.log-[Current thread is 1 (Thread 0x74ecf000 (LWP 629))]
kodi_crashlog_20170306002511.log-
--
kodi_crashlog_20170306004312.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306004312.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306004312.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306004312.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306004312.log-#0 malloc_consolidate ([email protected]=0x73c00010) at malloc.c:4204
kodi_crashlog_20170306004312.log-[Current thread is 1 (Thread 0x512ff3a0 (LWP 1016))]
kodi_crashlog_20170306004312.log-
--
kodi_crashlog_20170306021431.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306021431.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306021431.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306021431.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306021431.log-#0 0x698ac684 in ?? ()
kodi_crashlog_20170306021431.log-[Current thread is 1 (Thread 0x66dff3a0 (LWP 1122))]
kodi_crashlog_20170306021431.log-
--
kodi_crashlog_20170306022337.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306022337.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306022337.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306022337.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306022337.log-#0 0x76f7cb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306022337.log-[Current thread is 1 (Thread 0x74f0e000 (LWP 1334))]
kodi_crashlog_20170306022337.log-
--
kodi_crashlog_20170306034739.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306034739.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306034739.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306034739.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306034739.log-#0 0x76ee8b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306034739.log-[Current thread is 1 (Thread 0x74e7a000 (LWP 1494))]
kodi_crashlog_20170306034739.log-
--
kodi_crashlog_20170306043401.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306043401.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306043401.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306043401.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306043401.log-#0 0x76f4bb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306043401.log-[Current thread is 1 (Thread 0x74edd000 (LWP 1733))]
kodi_crashlog_20170306043401.log-
--
kodi_crashlog_20170306073316.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306073316.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306073316.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306073316.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306073316.log-#0 0x76f3cb64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306073316.log-[Current thread is 1 (Thread 0x74ece000 (LWP 1931))]
kodi_crashlog_20170306073316.log-
--
kodi_crashlog_20170306073949.log:[Thread debugging using libthread_db enabled]
kodi_crashlog_20170306073949.log-Using host libthread_db library "/usr/lib/libthread_db.so.1".
kodi_crashlog_20170306073949.log-Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd'.
kodi_crashlog_20170306073949.log-Program terminated with signal SIGSEGV, Segmentation fault.
kodi_crashlog_20170306073949.log-#0 0x76f98b64 in memcmp () from /usr/lib/libarmmem.so
kodi_crashlog_20170306073949.log-[Current thread is 1 (Thread 0x74f2a000 (LWP 2304))]
kodi_crashlog_20170306073949.log-
Display More
Thx! Sadly has no influence
Question:
How do I set MALLOC_MMAP_THRESHOLD by hand on RPi? It gets set from within kodi-config for 64bit, but DaveBlake wanted me to test with MALLOC_MMAP_THRESHOLD_=32768
kodi-config is read only and /run/libreelec/kodi.conf gets overwritten each time kodi starts, so I couldn't set it there.
I tried setting it as environment variable and
make me believe I've done it right.
Any other way?
On the mem leak, this is the last entry in mysql.log:
363 Connect [email protected] as anonymous on
363 Query SET NAMES utf8
363 Query SET SESSION sql_mode = (SELECT REPLACE(@@SESSION.sql_mode,'O
LY_FULL_GROUP_BY',''))
363 Query SELECT @@SESSION.optimizer_switch
363 Query SET SESSION optimizer_switch = 'derived_merge=off'
363 Query show databases like 'MyMusic60'
363 Query show tables
363 Init DB MyMusic60
363 Query show databases like 'MyMusic60'
363 Query show tables
363 Query SELECT COUNT(1) FROM songview WHERE ((CAST(songview.iTimesP
ayed as DECIMAL(5,1)) < 1))
363 Query SELECT songview.*, songartistview.* FROM songview JOIN songa
tistview ON songartistview.idsong = songview.idsong WHERE ((CAST(songview.iTimesPlayed as D
CIMAL(5,1)) < 1)) ORDER BY songartistview.idsong, songartistview.idRole, songartistview.iOrd
r
Display More
And this is kodi.log
jGTU
Here's a video
Dropbox - VID_20170227_221841.mp4
Update to 8.0.0c worked nicely as all updates before. Only thing is, the MAC of my ethernet controller changed!?
Thx for a great piece of software for that tiny little box
Ok, so after I got my music source scanned in (did switch from Mysql to a recent MariaDB which speeds up music scanning from 19h to 5h) the mem leak is definitely connected to using Xonfluence (guess it's skin.widget addon or library data provider, which come along with Xonfluence) together with a huge music source (130k files).
I'll provide logs!
Same setup on my s905x box is working great... so it's only the RPi3...