Jump to content

continuous crashing of kodi when synchronising


Littletycoon

Recommended Posts

Littletycoon

I'm desperate. I have continous kodi crashes when trying to synchronise the library with emby for kodi. I've tried appr. everything now including clean installs byt to no avail. I'm running on kodi 17 beta 5 and emby beta server.

 

I've tried everything, from limiting server request to as low as 10 in the addon settings, activating the database lock fix, but doesn't help. I don't et any crash indication in the the kodi logs. The only indication i get from the emby server log is (see blue highlighted):

 

2016-11-07 11:35:43.4526 Info HttpServer: HTTP Response 200 to 192.168.1.102. Time: 1ms. http://192.168.1.102:8096/emby/Items/a4a521bd49d745b18489d5b13ce69e0b/Images/Backdrop/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=9e66cb15d558d5436ac5175ac3e295a1 2016-11-07 11:35:43.4526 Info HttpServer: HTTP GET http://192.168.1.102:8096/emby/Items/a4a521bd49d745b18489d5b13ce69e0b/Images/Backdrop/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=9e66cb15d558d5436ac5175ac3e295a1. UserAgent: Kodi/17.0-BETA6 (Windows NT 10.0; WOW64) App_Bitness/32 Version/17.0-BETA6-Git:20161106-af8af7c 2016-11-07 11:35:43.5247 Info HttpServer: HTTP Response 206 to 192.168.1.102. Time: 67ms. http://192.168.1.102:8096/emby/Items/a4a521bd49d745b18489d5b13ce69e0b/Images/Backdrop/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=9e66cb15d558d5436ac5175ac3e295a1 2016-11-07 11:35:43.5362 Info HttpServer: HTTP Response 206 to 192.168.1.102. Time: 91ms. http://192.168.1.102:8096/emby/Items/270d05719055925b83eef205d3c583eb/Images/Primary/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=3f8289bdd8d526b1f5ada20910d9c4be 2016-11-07 11:35:43.5507 Info HttpServer: HTTP Response 206 to 192.168.1.102. Time: 106ms. http://192.168.1.102:8096/emby/Items/e5e5e3506fc1cd7e0cd3ecce419e832e/Images/Backdrop/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=b688afbddd2f02f4530a215fa006da9e 2016-11-07 11:36:05.6723 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 2016-11-07 11:37:36.7232 Info HttpServer: HTTP GET http://localhost:8096/emby/Users/af1642de416f45b1ac44ee25f3ec664a. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393 2016-11-07 11:37:36.7766 Info HttpServer: HTTP Response 200 to ::1. Time: 53ms. http://localhost:8096/emby/Users/af1642de416f45b1ac44ee25f3ec664a 2016-11-07 11:37:36.8965 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393 2016-11-07 11:37:36.8965 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393 2016-11-07 11:37:36.8965 Info HttpServer: HTTP Response 200 to ::1. Time: 4ms. http://localhost:8096/emby/System/Logs 2016-11-07 11:37:36.9085 Info HttpServer: HTTP Response 200 to ::1. Time: 12ms. http://localhost:8096/emby/System/Configuration 2016-11-07 11:37:40.0134 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/Log?name=server-63614111697.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393

 

A few seconds after this message in the emby server log, kodi crashes.

 

What does this error mean? How can I fix it?

Link to comment
Share on other sites

Angelblue05

The error simply means Kodi disconnected unexpectedly. Please post your Kodi log anyway, just so it can give us a better sense of what might be causing the crash.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Littletycoon

Follow up: During my last post I disabled force artwork caching in the add on settings and now kodi is not crashing anymore (at least synchronising is continuing beyond the previous crash point, i'm holding my breath that now my 70K music songs will syncrhonise without kodi crashing).

 

Apparently the crash was artwork caching related. What does this setting in the addon actually do and what could have been the reason for the continous crashes?

  • Like 1
Link to comment
Share on other sites

Angelblue05

Interesting, what device are you running this on? Which Kodi version are you running?

 

It forces your Emby artwork to be cached in Kodi as your content is imported. This allows for artwork to display right away for everything rather than wait for Kodi to cache artwork automatically (it's a much slower process as Kodi only caches artwork when the content is shown on the screen)

 

 

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

Littletycoon

kodi.logI'm running it on windows 10, up to date, on a corei3 broadwell chipset. Kodi version is latest beta, but i have this issue for months now with all krypton versions. I can't remember Jarvis since i'm on krypton versions for over 5 months now.

 

It took nearly 10 hours to sync, but without the artwork caching on the sync succeeded. However my woes have now moved on to scrolling the library, where kodi still crashes, when scrolling to certain parts of the library. There more than one crashpoints, but i can't single out the specific culprit due to the size of my library of 70K songs. Apparently the when kodi wants to cache the artwork from emby when it must be shown on screen, it crashes. Therefore the initial issue is still there.

 

I've attached a Kodi log (apparently can't attach the crashdump file).

 

 

 

 

Link to comment
Share on other sites

Angelblue05

Your log shows nothing regarding any crashing. If Kodi is crashing while navigating then it's a Kodi issue. The add-on just populates the database with Emby information and Emby artwork (plain http links). I have tested Krypton without issue on windows 10 core i7.

 

Do you have any other devices you can test on? Otherwise, please open a new thread on the official Kodi forums regarding your issue navigating and artwork loading and I'll tag along to see what the Kodi devs have to say. I don't think the issue is truly with Emby for Kodi as the caching mechanism is entirely Kodi (when we use it, we use the Kodi api to cache artwork)

Link to comment
Share on other sites

Littletycoon

I will nick my wife's laptop tomorromw to test on, slower machine but should be ok. The only indication I get before the crash is following line in the kodi log: ERROR: CFFmpegImage::ExtractFrame: Could not decode a frame, this line seems to be consistent through all the crashes just before kodi hangs.

 

Thanks, i will post it on the kodi forum, will be tomorrow.
 

  • Like 1
Link to comment
Share on other sites

puithove

FYI - had nothing but trouble with Krypton Beta 4 & Beta 5 (and nightly builds inbetween) this was on multiple boxes.  Trouble was more than just the Emby add-on, but it did include the Kodi crash during Emby sync.  

 

I've been running one of the nightlies prior to Beta 4 and it's been very stable.  I'm not where I can get the build number right now unfortunately.

  • Like 1
Link to comment
Share on other sites

Angelblue05

The build number is part of the Kodi log, and will be indicated at the beginning of it.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

puithove

This is the nightly build that's been working well for me... it was just a bit before Beta4.  Later nightlies up through Beta5 acted poorly and/or ended up with the Kodi crash during the Emby Add-on sync.  I haven't yet tried any of the nightlies much later than Beta5.

 

KodiSetup-20161019-5813648-master

 

 

Edit:  Oh, I should probably mention this was on Windows.

Edited by puithove
Link to comment
Share on other sites

Littletycoon

An update from my side. After doing a complete New install with kodi Krypton beta 6 (last week thursday nightly) the issue disappeared, out of the blue. Apparently something in kodi, but persistent in quite some Krypton versions. In the Mean Time i also found a lot of corrupt artwork and nfo's from an emby sync early november, whether related i would nog dare to say. Happy it's working again. Last test Will be syncing my music again, my primary reason to use emby for kodi

  • Like 1
Link to comment
Share on other sites

Angelblue05

Krypton has been a bumpy ride for a lot of people. Glad you got your setup to work.

 

 

Sent from my iPhone using Tapatalk

Edited by Angelblue05
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...