Kodi Community Forum

Full Version: Kodi crashing when starting video playback
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I've disabled scan on startup.
I have manually patched the tvdb.xml.
I have updated "metadata.tvdb.com" to the new version.
I have renamed all TV-related *.nfo files to *.nfo_ so that they're not scanned.
I have removed all addons that even mention tvdb.com, including:
- metadata.tvdb.com
- metadata.tvshows.themoviedb.org
- script.artwork.beef
- script.artwork.helper
- script.extendedinfo
- script.grab.fanart
- script.module.metadatautils
- script.module.metahandler
- script.module.thetvdb
- script.module.trakt
- script.trakt
- script.tv.show.next.aired

... but still Kodi freezes on the first frame of any video i play!

Here's the crashlog: amexiwucew.kodi (paste) - any thoughts?
Just as a sidenote, this box has been behaving exceptionally well up to the point that TVDB switched to their new API. :-(
@jangrewe

(2019-08-04, 23:17)jangrewe Wrote: [ -> ]... but still Kodi freezes on the first frame of any video i play!
You are describing a problem unrelated to scraping. I will split your post and move you to the Linux forum where others can help.

The log is only 4 seconds long and does not capture the freezing when playing. Can you provide another log which captures the problem. Thanks.

At this stage, you should reinstate those add-ons you removed as scraping has no affect on the videoplayer.
@Karellen i noticed i pasted the wrong log and already updated the link to a longer one which includes the playback of the video.

The interesting thing is that the behaviour is indeed absolutely identical to what i noticed when TVDB switched their API, e.g. that the load rises >60 as soon as the playback starts. Just no segfaults in dmesg anymore, since the fixed regex.

update: for the sake of it, here's another one with all addons enabled again: upewehikat.kodi (paste)
Please upgrade mess to 19.x looks like you are hit by the amd driver update outtage.

If you install gdb as well we might see it in the bacjtrace.
@fritsch as you can see from the logs, i'm already running Mesa 19.0.2 - if that's what you meant ;-)

I'll install gdb and force the crash again when i get home...
Yes, exactly :-) - please use 19.0.7 - but post your backtrace before that.
@fritsch Here you go, full crashlog with traces: yetibiceno.kodi (paste)
Ah, sweet relief! I installed Mesa 19.0.8 (the latest i could find as a package) from this guide, and now videos can be played again.

Thank you, @fritsch!
You are welcome.
@fritsch Unfortunately i spoke too soon... I had shut the box down after every was (seemingly) working fine again, went for a run and now wanted to enjoy some entertainment - and it reproduceably freezes at the first frame again. It's still Mesa 19.08, too.

The paste was a bit too big for the official pastebin, so here it is somewhere else: https://paste.ubuntu.com/p/s9HtXJp9HS/
Same behavior with Mesa 19.1.2 from https://launchpad.net/~paulo-miguel-dias...ntu/pkppa/ :-(
My final straw was to blacklist the "amdgpu" module, and after a reboot i was able to play an SD video just fine.
Then another reboot to confirm this wasn't a fluke, and... it freezes again.

I'm now completely out of ideas! :-(

If it's of any help, here's the latest crashlog: https://paste.ubuntu.com/p/2Xwgfs5nQn/
(2019-08-06, 17:28)jangrewe Wrote: [ -> ]My final straw was to blacklist the "amdgpu" module, and after a reboot i was able to play an SD video just fine.
Then another reboot to confirm this wasn't a fluke, and... it freezes again.

I'm now completely out of ideas! :-(

If it's of any help, here's the latest crashlog: https://paste.ubuntu.com/p/2Xwgfs5nQn/
It's still crashing inside the Mesa driver during VDPAU. You can file a bug with Mesa: https://bugs.freedesktop.org/. If you install debug symbols for the Mesa driver, it'll help debug the problem in the driver. You can install mesa-vdpau-drivers-dbgsym and libgl1-mesa-dri-dbgsym. When it crashes, you'll get the call stack in the driver in the stack trace instead of ?? for radeonsi_dri.so.

I see an existing bug for that assert that mentions a crash using VDPAU with Kodi and mpv: https://bugs.freedesktop.org/show_bug.cgi?id=107666

As a workaround, disable VDPAU hardware acceleration in Kodi. You can use VAAPI instead and still get hardware acceleration.
Unfortunately i don't have either of those packages available, even when going back to the stock repo with Mesa 19.0.2 instead of the PPAs.
But at least without HW accel videos play again, even 1080p HEVC. The CPU Usage is a bit high for my taste, but i guess my only option is now to wait for fixed Mesa drivers?

Thanks either way, @yasij! :-)
(2019-08-06, 19:34)jangrewe Wrote: [ -> ]Unfortunately i don't have either of those packages available, even when going back to the stock repo with Mesa 19.0.2 instead of the PPAs.
But at least without HW accel videos play again, even 1080p HEVC. The CPU Usage is a bit high for my taste, but i guess my only option is now to wait for fixed Mesa drivers?

Thanks either way, @yasij! :-)
Debug symbol packages are kept in a separate repository, and it's not enabled by default on Ubuntu. Instructions: https://wiki.ubuntu.com/Debug%20Symbol%20Packages. You have to enable the repository, and then they should show up for the stock Mesa. I don't know if the PPA builds them.

You should still have hardware acceleration using VAAPI instead of VDPAU. VAAPI is supposed to still work.

That bug report has been there since August with one comment in October. If you want the drivers to be fixed, you'll have to add comments and help the AMD driver writers. I don't have any AMD hardware so I can't help.
Pages: 1 2