[SOLVED] Kodi freezes on exit, kodi.bin won't die

pressman57 · 08-28-2016, 10:38 AM

Hi all. I have Kodi installed on two boxes, a desktop (Arch) and a laptop with Ubuntu Mate I use as a home theater hooked up to the TV. Both randomly freeze when trying to exit, I'd say 50% of the time. If I use Mate's force quit tool top shows kodi.bin still running. killall kodi.bin does nothing. Neither does kill pid number. The only way to kill it is to log out. Any ideas how on how to exit Kodi cleanly?

Rinndalir · 08-29-2016, 02:00 PM

Next time it happens run strace on the Kodi.bin. Also what kodi version?

And kill -9 <pid of kodi.bin> will kill it.

pressman57 · 08-29-2016, 06:40 PM

Yep kill -9 worked. Thanks. Now I've gotta figure out why Kodi's freezing in the first place...

I'm running the current Arch kodi-16.1-4 with TVaddons, which is probably the problem. I'm waiting for the next freeze to look at the logs.

Thanks again

Rinndalir · 09-01-2016, 06:33 PM

Quote:

Originally Posted by pressman57

current Arch kodi-16.1-4 with TVaddons, which is probably the problem. I'm waiting for the next freeze to look at the logs.

The addons are big source of problems and it seems to be constant. I think Kodi devs need to really give Kodi a complete overhaul. The interface is terrible. I'd rather just use ffplay song.mp3 or ffplay video.mp4 than use that interface.

They should make a 3 month feature freeze and only fix the UI and bugs. They should also insist on better code for the addons. Possibly through continuous integration results. They really need to circle the wagons on the product and make the basics work consistently and reliably.

Emerson · 09-01-2016, 08:36 PM

The only way I got everything (plugins) working was to pull sources from git and build everything by hand.

Rinndalir · 09-02-2016, 04:23 PM

Quote:

Originally Posted by Emerson

The only way I got everything (plugins) working was to pull sources from git and build everything by hand.

Yeah way too much work for way too little benefit for me to do that. And it is sad that's required at all.

PiroXiline · 12-19-2016, 07:48 PM

Hey, people. I just solved that with minor workaround and wrote solution to ArchWiki.
Look here: https://wiki.archlinux.org/index.php...I_unresponsive