Posts: 9
Joined: Jan 2017
Reputation:
0
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%.
Posts: 66
Joined: Jul 2014
Reputation:
2
2017-03-02, 06:53
(This post was last modified: 2017-03-02, 06:58 by normadize.)
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.
Posts: 66
Joined: Jul 2014
Reputation:
2
Is there a bug open for this in the bug tracker anywhere?
Posts: 1,897
Joined: Feb 2013
Reputation:
128
crash still occurs inside a driver.
Posts: 200
Joined: Apr 2007
Reputation:
4
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.6 on multiple Windows 10 x64 machines with shared MySQL 5.6.43 database. Kodi 18 on Xbox One. Content (music, video, photos) stored on Windows Server 2012 R2 file server and accessed by SMB.
Posts: 1,897
Joined: Feb 2013
Reputation:
128
we (Kodi developers) shouldn't cure not own issue. especially because the curing it requires patching ffmpeg code base. report the issue to Intel.
Posts: 66
Joined: Jul 2014
Reputation:
2
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
Posts: 9
Joined: Jan 2017
Reputation:
0
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.
Posts: 195
Joined: Jan 2016
Reputation:
1
2017-04-26, 09:19
(This post was last modified: 2017-04-26, 09:21 by mamachan.)
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