+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59)
+---- Thread: Bug Crashes when trying to resume playback of x265 from time X (/showthread.php?tid=289533)
RE: Crashes when trying to resume playback of x265 from time X - Com_DAC - 2017-07-19
@xbmcoholic anything that might help get this issue resolved
Anyone else here having this issue please chime in on the intel forum @ https://communities.intel.com/thread/116386 The more people that add to that post the more likely intel might pay attention.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-07-20
It seems that if you have a 5th (5xxx) Generation Intel CPU or older, having DXVA2 turned on or off should have no performance impact as DXVA2 support isn't introduced until the 6th Generation and up.
https://www.intel.com/content/www/us/en/processors/core/core-technical-resources.html
The Intel thread on crashes is still going, they had no crashes on the latest hardware and drivers but were able to replicate the issue on the older driver which is current for my hardware. My gut tells me that they'll probably post an updated driver for the older hardware that makes sure DXVA2 is completely disabled which is essentially the same thing as the work-around of disabling DXVA2 in the advanced Kodi Player settings.
RE: Crashes when trying to resume playback of x265 from time X - Com_DAC - 2017-07-21
When I turn on DXVA2 and playback HEVC content it uses quite noticiably less cpu and videos that would stutter with it off run smooth.
With DXVA2 turned off pressing "O" (codec info) while playing a video shows it as software decoding. The DXVA2 turned on pressing "O" it shows it as hardware decoding and shows the lower cpu usage.
If DXVA2 isn't support why does enabling it cause smoother playback and a decrease in cpu usage?
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-07-21
(2017-07-21, 22:40)Com_DAC Wrote: When I turn on DXVA2 and playback HEVC content it uses quite noticiably less cpu and videos that would stutter with it off run smooth.
With DXVA2 turned off pressing "O" (codec info) while playing a video shows it as software decoding. The DXVA2 turned on pressing "O" it shows it as hardware decoding and shows the lower cpu usage.
If DXVA2 isn't support why does enabling it cause smoother playback and a decrease in cpu usage?
Sorry @Com_DAC - I tested a few more times and noticed a little bit of increased CPU usage with Sofware and DXVA only, DXVA2 had a little bit lower CPU utilization but not much. It's probably just the difference between our systems which causes DXVA2 has a much more noticeable impact.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-07-21
Intel has filed a bug related to this now.
Intel bug ID# 1406352370.
They mentioned that future dev work will likely be focused on 6th and 7th gen chips. Can anyone confirm if this happens on 6th gen or is this only a problem with 5th gen which both myself and Com_DAC use?
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-07-28
Hey Guys,
Someone from Intel is looking to work directly with the Kodi team on this. Are any devs available to help? Let me know and I'll connect the dots.
RE: Crashes when trying to resume playback of x265 from time X - fbi1970 - 2017-08-01
Any news about this bug? I've a NUC D54250WYKH2 (Intel HD 5000) with same behaviour. Even if it can be the Intel driver I've a friend of mine which have same behaviour with Plex App on a Smart TV and you can find out same bug on plex. So, this leads me to think it's a Kodi bug. Please Kodi developers, look into this issue because this year and next year we'll pass from x264 to x265 and, at the moment, Kodi shows a terrible bug.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-08-31
Again, if any devs are interested in working with Intel on this please respond.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-09-01
I've copied intel's response below: (edited to condense)
Go ahead and share this with Kodi, I think the more devs look at it the faster they can work on a fix within the application code.
If on the other hand, they would like to dispute the debug results, I think the best place would be transferring the conversation to the Intel Developer Forum and reference internal Bug ID 1406352370.
It seems that this time, the stacks of the exception causing thread and call stack are same, i.e. exception has not gone by. And the stack points to the application (Kodi player).
This is not a GFX driver issue since igd10umd32 related tasks were executing properly.
Needs to be checked with Kodi development.
0:030> g
ModLoad: 00000000`6ab40000 00000000`6aba7000 C:\windows\SysWOW64\TextInputFramework.dll
ModLoad: 00000000`6aab0000 00000000`6ab3f000 C:\windows\SysWOW64\CoreMessaging.dll
ModLoad: 00000000`6a880000 00000000`6aaa7000 C:\windows\SysWOW64\CoreUIComponents.dll
ModLoad: 00000000`6a850000 00000000`6a878000 C:\windows\SysWOW64\ntmarta.dll
ModLoad: 00000000`6a770000 00000000`6a841000 C:\windows\SysWOW64\wintypes.dll
ModLoad: 00000000`6a760000 00000000`6a770000 C:\windows\SysWOW64\usermgrcli.dll
ModLoad: 00000000`0d470000 00000000`0d541000 C:\windows\SysWOW64\wintypes.dll
ModLoad: 00000000`0d470000 00000000`0d541000 C:\windows\SysWOW64\wintypes.dll
ModLoad: 00000000`68590000 00000000`6a760000 C:\windows\SysWOW64\igd11dxva32.dll
D3D11: Removing Device.
(cd4.e9c): C++ EH exception - code e06d7363 (first chance)
(cd4.e9c): C++ EH exception - code e06d7363 (first chance)
(cd4.e9c): C++ EH exception - code e06d7363 (first chance)
(cd4.e9c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
*** WARNING: Unable to verify checksum for C:\Program Files (x86)\Kodi\kodi.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files (x86)\Kodi\kodi.exe
ntdll_76f50000!RtlEnterCriticalSection+0x13:
76f9b263 f00fba3000 lock btr dword ptr [eax],0 ds:002b:00000024=
??Current thread:
0:033:x86> ~.
. 33 Id: cd4.e9c Suspend: 1 Teb: 0051c000 Unfrozen "VideoPlayerVideo"
Start: *** ERROR: Symbol file could not be found. Defaulted to export symbols for ucrtbase.dll -
ucrtbase!set_app_type+0x10 (7641e840)
Priority: 0 Priority class: 32 Affinity: f
Call stack for current thread(exception):
0:033:x86> ~.k
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be wrong.
00 10f8f450 0156b3cb ntdll_76f50000!RtlEnterCriticalSection+0x13
01 10f8f490 0157fdd6 kodi+0x6cb3cb
02 10f8f514 0155389d kodi+0x6dfdd6
03 10f8f52c 014c532b kodi+0x6b389d
04 10f8f5b0 014ccc31 kodi+0x62532b
05 10f8f718 014cd7fa kodi+0x62cc31
06 10f8f76c 014cd49f kodi+0x62d7fa
07 10f8f7cc 0101f6ea kodi+0x62d49f
08 10f8f804 01020001 kodi+0x17f6ea
09 10f8f884 7641e87f kodi+0x180001
*** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNEL32.dll -
0a 10f8f8c0 73ad8744 ucrtbase!set_app_type+0x4f
0b 10f8f8d4 76fb587d KERNEL32!BaseThreadInitThunk+0x24
0c 10f8f91c 76fb584d ntdll_76f50000!RtlGetAppContainerNamedObjectPath+0xfd
0d 10f8f92c 00000000 ntdll_76f50000!RtlGetAppContainerNamedObjectPath+0xcd
Call Stack:
0:033:x86> k
# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be wrong.
00 10f8f450 0156b3cb ntdll_76f50000!RtlEnterCriticalSection+0x13
01 10f8f490 0157fdd6 kodi+0x6cb3cb
02 10f8f514 0155389d kodi+0x6dfdd6
03 10f8f52c 014c532b kodi+0x6b389d
04 10f8f5b0 014ccc31 kodi+0x62532b
05 10f8f718 014cd7fa kodi+0x62cc31
06 10f8f76c 014cd49f kodi+0x62d7fa
07 10f8f7cc 0101f6ea kodi+0x62d49f
08 10f8f804 01020001 kodi+0x17f6ea
09 10f8f884 7641e87f kodi+0x180001
0a 10f8f8c0 73ad8744 ucrtbase!set_app_type+0x4f
0b 10f8f8d4 76fb587d KERNEL32!BaseThreadInitThunk+0x24
0c 10f8f91c 76fb584d ntdll_76f50000!RtlGetAppContainerNamedObjectPath+0xfd
0d 10f8f92c 00000000 ntdll_76f50000!RtlGetAppContainerNamedObjectPath+0xcd
RE: Crashes when trying to resume playback of x265 from time X - afedchin - 2017-09-01
@xbmcoholic,
What you want to know? Intel driver is crashed and causes D3D11 Removing Device in any random place. because decoding video and rendering are parallel. It occurs only on decoding x265, no crashes on other videos, no crashes on other GPUs. You can quote my message on Intel forum.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-09-01
@afedchin,
Thanks for responding, I've copied this over to the Intel forum. Is there a specific log excerpt I can show them to highlight the issue of the driver crashing - D3D11 Removing Device - which in turn causes Kodi to crash? Anything you think a driver developer would find helpful or at the very lease show as proof?
EDIT: Sorry I see the D3D11 Removing device log above
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-09-13
Just an FYI for anyone that comes across this thread. I've hit a dead end with Intel as their support forum states that no driver updates are planned for 5th Gen intel chips. If you have a 5th Gen intel chip and you don't want Kodi to crash when resuming HEVC / h265 videos, ENABLE DXVA but DISABLE DXVA2.
If on the other hand, anyone would like to dispute the debug results, please start the conversation on the Intel Developer Forum(https://communities.intel.com/external-link.jspa?url=https%3A%2F%2Fsoftware.intel.com%2Fen-us%2Fforum) and reference internal Bug ID 1406352370.
I'm not a developer and cant speak to details which would have any meaningful impact, I've taken this as far as I can.
RE: Crashes when trying to resume playback of x265 from time X - Com_DAC - 2017-12-23
So it looks like Intel has now officially given us the shaft: https://communities.intel.com/thread/116386 Their options are disable the feature or buy a newer NUC. Way to go Intel.
RE: Crashes when trying to resume playback of x265 from time X - xbmcoholic - 2017-12-23
(2017-12-23, 14:28)Com_DAC Wrote: So it looks like Intel has now officially given us the shaft: https://communities.intel.com/thread/116386 Their options are disable the feature or buy a newer NUC. Way to go Intel.https://giphy.com/gifs/teamcoco-crying-cry-l2JhtKtDWYNKdRpoA/fullscreen
RE: Crashes when trying to resume playback of x265 from time X - malvinas2 - 2018-01-11
(2017-12-23, 14:28)Com_DAC Wrote: So it looks like Intel has now officially given us the shaft: https://communities.intel.com/thread/116386 Their options are disable the feature or buy a newer NUC. Way to go Intel.I made one more attempt to convince Intel to support the Broadwell-Generation: https://communities.intel.com/message/519089#519089