[rtfanatic360]

Hello all,
Ive been searching through forums and have not been able to find this issue yet. I am running an Asus Chromebox I3 dualbooting Chrome/Openelec. The problem im having is while watching videos either locally (Nas Drive) or streaming through a video addon I get very random restarts back to Kodi home page. I dont get a full system reboot just a Kodi reboot. This could happen after 30 minutes or 3 hours. I have enabled debugging and component specific debugging, and have been scanning through the logs to see what I can make out but the .old logs are not going to the time of crash, there is a gap of about 30 minutes before it crashes. Maybe I need to do a different type of debug for less spam? Or is there a different log for crash? Here is my last .old log in case Im missing something. Any help is appreciated
Thanks.
http://xbmclogs.com/pf7taphc4 (Crash was at 11:39, new log starts after reboot)

[rtfanatic360]

happened again at 14:31 but .old log stops at 13:53?

[rtfanatic360]

xbmclogs.com/pocgdgij3

Here is a recent log. Crash happened at 15:21 but nothing in log for that time?

[rtfanatic360]

Any ideas? has crashed a few more times but the logs all stop 15-20 minutes before the crash?

[Milhouse]

To be honest, debug logs are pretty much useless when Kodi is crashing. What's needed is a crash log, but you'll need to upgrade to a master build of OpenELEC (which is based on Kodi 15) for that.

[DaVu]

It´s pretty simple...

You are using genesis to watch your videos. You can see it pretty fine before the reboot, that the addon wants to start but has some sync errors. We don´t support any of those banned addons:

http://kodi.wiki/view/Banned_add-on

So to get this solved:

remove those repositories:

14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.tknorris.release
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.lambda
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.superrepo.org.gotham.video
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.eldorado
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.xbmchub
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.superrepo.org.gotham.repositories
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.alelec
14:31:40 T:140343892752256 NOTICE: ADDONS: Using repository repository.eleazar

and with them, remove all of your installed banned addons. For the best way, I would rename the ".kodi" folder to "kodi-old" and reboot. Then you have a factory reset.

Then try to play back a file on your local network. A file which you really own and grab the log if it fails. If this still fails, please copy that file directly to your HTPC and play from there and grab the log again.

For less spam on those logs, please disable the "update library at startup" function. After any reboot, try to reproduce your issue as fast as you can and don´t do anything else.

We can´t do anything for you while you are using those addons or repositories. But there is a way to still use the addons and maybe get it solved with them....

Ask where you get this addon from


Milhouse:

AFAICS Kodi is not causing the "crash"/"reboot". It´s the addon.

[Milhouse]

Milhouse:

AFAICS Kodi is not causing the "crash"/"reboot". It´s the addon.

Yes, but there's no way to know what is actually causing the crash and where, without a crashlog and seeing the call stack.

It's probably the add-on going nuts and bringing down Kodi, but it could also be doing something completely normal and inadvertently triggering a genuine bug in core. It might even be nothing to do with the add-on, although the chances of that are probably slim...

[rtfanatic360]

Thanks for the reply. I get the issue playing local network files as well. I will try upgrading to master build for more crash log data, and see if i still get issue with master build, and i will make sure no banned addons are installed. Thanks again for all your help.

[rtfanatic360]

UPDATE:
I have updated using a test build from the Media importing and library integration of UPnP thread, for crash log info. I have also renamed .kodi to .kodi-old for a fresh install. All I have done is add my Local Network movies and played a file and it is still crashing. Here is the most recent crash log from SSH terminal

http://pastebin.com/QCMEZ7MZ

[Milhouse]

As this seems to be JSON related, in System -> Debugging, can you enable "component specific logging" then in the "specify component specific logging" section, enable "Verbose logging for JSON-RPC requests", and then try to create another crashlog.

I'm wondering if a debug-enabled build might provide more details in the crashlog, I'll upload a new build in a few hours.

[rtfanatic360]

As this seems to be JSON related, in System -> Debugging, can you enable "component specific logging" then in the "specify component specific logging" section, enable "Verbose logging for JSON-RPC requests", and then try to create another crashlog.

I'm wondering if a debug-enabled build might provide more details in the crashlog, I'll upload a new build in a few hours.

This log is really long, took a while to crash this time. I will play another movie and try to get a shorter log

http://pastebin.com/dMqwsPMR
http://xbmclogs.com/pkqevtdhx And this is the Kodi log from Log share

[Milhouse]

That log has lost the top of the file - xbmclogs.com may allow longer log files than pastebin.com - so it's impossible to know if the crash coincided with a particular JSON query.

Are you using a smartphone/tablet app to control Kodi, that may be the source of all the JSON queries. At some stage, disabling the app on all devices may be a useful test.

The new debug-enabled build has been delayed, but should be there soon.

[rtfanatic360]

That log has lost the top of the file - xbmclogs.com may allow longer log files than pastebin.com - so it's impossible to know if the crash coincided with a particular JSON query.

Are you using a smartphone/tablet app to control Kodi, that may be the source of all the JSON queries. At some stage, disabling the app on all devices may be a useful test.

The new debug-enabled build has been delayed, but should be there soon.

I am using Control4 IP driver (Automation) to control Kodi?
Edit: Yes the Control4 driver is the one making those JSON queries

[rtfanatic360]

heres another crash

http://xbmclogs.com/p3ospymtw

[Milhouse]

http://xbmclogs.com/pkqevtdhx And this is the Kodi log from Log share

This is a different crash than before, and doesn't seem to be JSON related.

heres another crash

http://xbmclogs.com/p3ospymtw

The stacktraces are still chopped off.

Here's a debug-enabled build, without the WIP UPnP patches (364 MB download):

Generic/x86_64: http://milhouse.openelec.tv/builds/debug...42706d.tar