Thread Rating:
  • 1 Vote(s) - 5 Average
BUG - Crashes when trying to resume playback of x265 from time X
#16
I've been seeing the same issue. Currently using Windows 10 x64, Intel HD 5500 and Kodi 17.0 RC2 (same happened in 16.1). Tried many different graphic driver versions and I've increased the amount of memory allocated to the GPU to the max (1GB from 256MB) and it still freezes. Disabling DXVA2 solves the resume problem but my cpu usage on newer HEVC content runs over 90% where with DXVA2 enabled it sits at 45%.
Reply
#17
Same issue on Skylake i5-6500T and Kodi 17.1 RC1 in WIndows 8.1 x64. Intel driver version 21.20.16.4542.

As the others, crash only happens when resuming x265 encoded files. Quite annoying.

EDIT: Sometimes it worked but I think it was because the file was encoded with --no-open-gop.
Reply
#18
Is there a bug open for this in the bug tracker anywhere?
Reply
#19
I created a bug on tthe tracker: http://trac.kodi.tv/ticket/17368 (searched and couldn't find one there)
Reply
#20
Just hit this issue for the first time (only just starting to use more HEVC encoded content).

Kodi 16.1 on Windows 10 x64
Hardware: Intel NUC D54250WYK (4th Gen)
CPU: Intel Core i5-4250U processor
Chipset: Intel Haswell
Graphics: Intel HD Graphics 5000 (driver will be whatever Windows Update has pushed down)
RAM: 8GB RAM

The file causing issue had "open-gop" as part of encoding parameters.

My workaround is to resume from start of movie and fast-fwd up to the point I want to resume from Smile
Kodi 17.3 on multiple Windows 10 x64 machines, shared MySQL 5.6.36 database, content stored on Windows Server 2012 R2 file server.
Reply
#21
Have continued seeing this with Kodi 17.1

In case anyone wants to review/validate:
* Kodi Debug Log here - https://pastebin.com/9FDPaYZz (or here http://pastebin.ca/3799048)
* Stack trace and dump file - http://anthonyb.no-ip.biz/kodicrash.rar
Kodi 17.3 on multiple Windows 10 x64 machines, shared MySQL 5.6.36 database, content stored on Windows Server 2012 R2 file server.
Reply
#22
crash still occurs inside a driver.
Reply
#23
I've tried 4 different Intel drivers going back as far as late 2015 and they all crash:

Driver version: 20.19.15.4624
Driver date: 8/03/2017

Driver version: 20.19.15.4444
Driver date: 22/04/2016

Driver version: 20.19.15.4331
Driver date: 20/11/2015

Driver version: 20.19.15.4300
Driver date: 01/10/2015

While I appreciate that the crash is originating from the Intel drivers, if we can't find a driver that works on what is a reasonably common hardware config, then from a user experience perspective we really should have Kodi work-around or at least prevent the crash from occurring.
Kodi 17.3 on multiple Windows 10 x64 machines, shared MySQL 5.6.36 database, content stored on Windows Server 2012 R2 file server.
Reply
#24
we (Kodi developers) shouldn't cure not own issue. especially because the curing it requires patching ffmpeg code base. report the issue to Intel.
Reply
#25
But if the problem was at Intel then how come none of my other windows players don't exhibit it? My VLC, media player classic, also mplayer (compiled by myself a while ago from ffmpeg sources SVN-r37598-5.3.0) don't have a problem. Is it really intel's or ffmpeg's fault? What am I missing?

Also, the problem only occurs when starting the play elsewhere other than 00:00:00s (seeking is otherwise fine) ... and only in Kodi
Reply
#26
(2017-04-20, 11:10)afedchin Wrote: we (Kodi developers) shouldn't cure not own issue. especially because the curing it requires patching ffmpeg code base. report the issue to Intel.

Totally agree.

That is why I said "then from a user experience perspective we really should have Kodi work-around or at least prevent the crash from occurring."

The issue occurs in every driver I tried over the last 18 months. It is Intel. Chances of finding a way "to report it to Intel" and get it resolved? I've worked for similar companies and issues like this when reported by random joe average from the general public go nowhere... If a Kodi dev could submit it then they can provide the technical evidence supporting the submission. If I submit it my evidence is essentially "a developer in a free open source community said your driver is the cause" Blush

If there is any way in Kodi we can work-around or prevent the issue from triggering, then from a broad user experience perspective, that will have broader and faster impact. If there is not, then so be it.
Kodi 17.3 on multiple Windows 10 x64 machines, shared MySQL 5.6.36 database, content stored on Windows Server 2012 R2 file server.
Reply
#27
A possible work around might to to introduce an alternative resume functionality where it starts playing from 00:00:00 then after the first few frames it skips to the resume point.
Reply
#28
Good morning,

(2017-04-20, 09:30)AnthonyB Wrote: I've tried 4 different Intel drivers going back as far as late 2015 and they all crash:

Driver version: 20.19.15.4624
Driver date: 8/03/2017

Driver version: 20.19.15.4444
Driver date: 22/04/2016

Driver version: 20.19.15.4331
Driver date: 20/11/2015

Driver version: 20.19.15.4300
Driver date: 01/10/2015

I also had this crashing problems with my Intel 5500HD NUC.

But yesterday I updated the Intel Drivers from V:20.19.15.4501 to V.20.19.15.4624 and that did the trick.
Reply
#29
Same issue on my system with HEVC h265
WIN 7 PRO 64bit
Intel i3-4330 HD4600
DXVA2 = ON

From a few days, furthermore, Kodi krashed after 10/20 min. when i play hevc h265 videos.
NO problem with MPC-HC, so i thinks is not a windows related problem
I did not make ANY updates these days
Reply
#30
(2017-04-26, 09:19)mamachan Wrote: NO problem with MPC-HC, so i thinks is not a windows related problem
please stop comparing different things. MPC-HC uses another API -> DirectX9. Kodi uses DirectX 11.
Reply
 
Thread Rating:
  • 1 Vote(s) - 5 Average



Logout Mark Read Team Forum Stats Members Help
Crashes when trying to resume playback of x265 from time X51