Crash (at the end of the movie)
#1
Hello,

Since upating to Xenial and Krypton, I get crashes quite reqularly. Most typically I get the crash at the end of a movie.
Many times after the crash, all terminals tty1-7 get blank. SSH is working.

Ubuntu server 16.04.2 LTS
17.0 Git:20170210-nogitfound

Here are some logs of the last crash.

dpkg -l | grep mesa http://paste.ubuntu.com/24029741/
DISPLAY=:0 vainfo http://paste.ubuntu.com/24029742/
cat ~/.kodi/temp/kodi.log http://paste.ubuntu.com/24029743/
dmesg http://paste.ubuntu.com/24029744/
id http://paste.ubuntu.com/24029745/
amixer http://paste.ubuntu.com/24029746/
cat /var/log/Xorg.0.log http://paste.ubuntu.com/24029747/

cat ~/kodi_crashlog-20170219_220218.log http://paste.ubuntu.com/24029959/

(After this, I tried to restart kodi with systemctl restart kodi, got new crash)

cat ~/kodi_crashlog-20170219_221103.log http://paste.ubuntu.com/24029961/

I can't make a lot out of the logs, except that it may be audio related.
Any help would be appreciated. Thank you.
Reply
#2
Two pa threads fight each other.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
(2017-02-20, 07:24)fritsch Wrote: Two pa threads fight each other.

Any hints how to fix / diagnose further?
Or is it a known issue? (I tried to check trac but I get internal error for any queries.)
Reply
#4
It's not known - you are the first hitting this issue. I will check the threads tonight and will see.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#5
Contacted Tanuk from PA project. Basically we still get mainloop messages while we stop it, which makes me wonder. Will keep you posted once I get an answer.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#6
(2017-02-20, 20:54)fritsch Wrote: Contacted Tanuk from PA project. Basically we still get mainloop messages while we stop it, which makes me wonder. Will keep you posted once I get an answer.

Thank you. Let me know if you need more logs etc.
Reply
#7
For the time being, you can use ALSA for playback - just start kodi with: AE_SINK=ALSA kodi
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
I also experience the memory leak (http://forum.kodi.tv/showthread.php?tid=307613), I wonder if this issue may be triggered by the leak?
Reply
#9
There is NO leak.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#10
Post your Debug Log. And don't mix things totally unrelated. The above issue is caused by memory fragmentation.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#11
I will post a debug log tonight.
Reply
#12
Here is the debug log:
dpkg -l | grep mesa
http://paste.ubuntu.com/24048131/
DISPLAY=:0 vainfo
http://paste.ubuntu.com/24048132/
cat ~/.kodi/temp/kodi.log
http://paste.ubuntu.com/24048133/
dmesg
http://paste.ubuntu.com/24048134/
id
http://paste.ubuntu.com/24048135/
amixer
http://paste.ubuntu.com/24048136/
cat /var/log/Xorg.0.log
http://paste.ubuntu.com/24048137/
journalctl -u kodi.service
http://paste.ubuntu.com/24048138/
cat kodi_crashlog-20170222_195056.log
http://paste.ubuntu.com/24048139/
Reply
#13
Yeah - same issue. No reply from my contact at pulseaudio yet.

If you feel like experimenting. Disable the combined device and try again please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#14
Disabled the combined and rebooted the pc, I got a crash immediately on kodi start:
dpkg -l | grep mesa
http://paste.ubuntu.com/24048211/
DISPLAY=:0 vainfo
http://paste.ubuntu.com/24048212/
cat ~/.kodi/temp/kodi.log
http://paste.ubuntu.com/24048213/
dmesg
http://paste.ubuntu.com/24048214/
id
http://paste.ubuntu.com/24048215/
amixer
http://paste.ubuntu.com/24048216/
cat /var/log/Xorg.0.log
http://paste.ubuntu.com/24048217/
journalctl -u kodi.service
http://paste.ubuntu.com/24048218/
cat kodi_crashlog-20170222_200645.log
http://paste.ubuntu.com/24048219/

With starting/stopping a video a few times, I can easily get more crashes:
dpkg -l | grep mesa
http://paste.ubuntu.com/24048304/
DISPLAY=:0 vainfo
http://paste.ubuntu.com/24048305/
cat ~/.kodi/temp/kodi.log
http://paste.ubuntu.com/24048306/
dmesg
http://paste.ubuntu.com/24048307/
id
http://paste.ubuntu.com/24048308/
amixer
http://paste.ubuntu.com/24048309/
cat /var/log/Xorg.0.log
http://paste.ubuntu.com/24048311/
journalctl -u kodi.service
http://paste.ubuntu.com/24048312/
cat kodi_crashlog-20170222_203037.log
http://paste.ubuntu.com/24048313/
Reply
#15
We need to build kodi from source and test an idea I just had to resolve this deadlock.
Code:
sudo apt-get build-dep kodi
mkdir ~/mykodi
cd ~/mykodi
git clone https://github.com/fritsch/xbmc.git
cd ~/mykodi/xbmc
git checkout -b flt origin/flt
cmake -DCMAKE_BUILD_TYPE=Debug
make -j8

Wait until compilation is finished. Then please start kodi with:
Code:
cd ~/mykodi/xbmc
./kodi.bin

What happens now?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Crash (at the end of the movie)0