v17 Updated Kodi to 17.3 - Receiving exception message upon exit
#1
Bug 
Hello Community!

This thread is specific to the latest version of RetroPie running on a Raspberry Pi 3 B+.

I recently performed an update of RetroPie and all operating system level updates.

One update was for Kodi from 17.1 to 17.3; after updating to Kodi 17.3 the following message appears upon exiting Kodi (Power Button > Exit) which causes a brief pause before returning to EmulationStation:
  • Exception SystemExit in (function _remove at 0x66bc1870) ignored
It's important to note that the same message appears when you relaunch Kodi.

So, the following questions come to mind:
  • Could the issue stem from how EmulationStation is opening Kodi?
  • Does anyone know if this is an issue specific to Kodi?
  • Is this an issue with RetroPie (and its updated components)?
  • Is this is an issue with the underlying operating system (and its updated components)?
I look forward to anyone's comments or suggestions; I've posted a similar topic/thread on RetroPie's forum.

Thank you!
Reply
#2
I am having the same problem on Raspbian with Kodi compiled from source, however Kodi won't shutdown at all, just hangs.

Would like to know if anyone comes up with anything also.
Reply
#3
You have my answer for this same question in the RetroPie forum here:
https://retropie.org.uk/forum/topic/1061...-upon-exit

Answering to the questions:
1- No.
2- Yes, it is.
3 and 4- No. The same may occur in other systems like Open/LibreELEC, if you enable the exit option. Tested this myself some time ago. Was unable to reproduce it now in a clean Kodi 17.3 install under Raspbian however.

PS: When It happens, it never completely hangs, it just takes more time to exit than normal and produce a crashlog.
Reply
#4
If you use popcornmix's (repo/patches) you could try this patch https://pastebin.com/3S99G98X
The diff is against current newclock5 which is Leia, but if backported may help with the crash on exit issue.

If anyone can confirm it helps I can PR it to popcornmix's repo.
Reply
#5
We use popcormix repo, but the stable branch, currently krypton_rbp_backports.
The code has changed for 18, so not sure if it will fix it and how to change it here:
https://github.com/popcornmix/xbmc/blob/....cpp#L1207
And then, if I find a way to reproduce it again, I can recompile it and test it.

PS: Just to make sure it is the same problem, it just occurs on "Exit", not on "Reboot" and "Shutdown" (at least it is pretty quick in this options, and doesn't produce a crashlog).
Reply
#6
Yep, the code has changed a lot, I'll take a look when I get home.
Reply
#7
Try this https://gist.github.com/asavah/18ce20ce2...fc0ec64d31
Reply
#8
Hi asavah,

I'm currently building off krypton_rbp_backports, your patch doesn't appear to have helped.

Crash report here if this is of any help. https://pastebin.com/AZusy3G8

This was produced after trying to stop Kodi with a systemctl command (which had no effect) and then exiting Kodi from menu. Systemd is setup correctly and there are no problems starting.

Without using systemctl first Kodi wont quit from the menu. It just hangs, nothing to report when debug logging.
kodi-eventclients-xbmc-send will kill Kodi with no problems.
Reply
#9
Wink 
@rascas and everyone who replied, thank you very much!

I'll review the advice that you have all given and will report back soon.

I will also try to see if I can get the kodi-standalone command to work within the kodi launch script.

Thanks again!
Reply
#10
(2017-05-30, 02:10)kjb85 Wrote: Hi asavah,

I'm currently building off krypton_rbp_backports, your patch doesn't appear to have helped.

Crash report here if this is of any help. https://pastebin.com/AZusy3G8

This was produced after trying to stop Kodi with a systemctl command (which had no effect) and then exiting Kodi from menu. Systemd is setup correctly and there are no problems starting.

Without using systemctl first Kodi wont quit from the menu. It just hangs, nothing to report when debug logging.
kodi-eventclients-xbmc-send will kill Kodi with no problems.

Sad

Hmm, the crash is completely different from what I was seeing in newclock5 (Leia), sorry but I can't provide further ideas because I lack the skill and the time and my environment is already tuned for Leia.
A good idea might be to have a debug build of kodi run through gdb, provoke the crash and make a full backtrace which could provide necessary clues to a skilled Kodi dev.

I also have this patch borrowed from LE https://github.com/LibreELEC/LibreELEC.t...TERM.patch
Reply
#11
@ kjb85, your problem seems to be different from the OP, so it is maybe better to open a new post.

@ ibro, using kodi-standalone won't help, it will get even worst, because if Kodi crashs on exit, it will restart again. Please enable debug like explained here http://kodi.wiki/view/log_file, and post the log when it happens again.
Reply
#12
Wink 
I found a potential solution, but I do not know if it'll work for everyone.

The script under /home/pi/RetroPie/roms/kodi/ had the following line:
  • sudo kodi
I changed it to read as follows:
  • kodi-standalone
I did not receive the Exception SystemExit in (function _remove at 0x66bc1870) ignored message.

I followed the guide here:
Reply

Logout Mark Read Team Forum Stats Members Help
Updated Kodi to 17.3 - Receiving exception message upon exit0