Crash watching IPTV with Krypton

Hi,

I have Kodi 17.1-RC2 Git:20170315-5814568, Windows 10 x64 1607 (build 14393.693), an i5-6400 and 8GB RAM. (I was previously using the main Krypton release from February 1st, but switched to nightly to reproduce.) My secondary, where Kodi is displayed, is 1920×1200 and attached via HDMI to an NVIDIA GeForce GTX 745 (driver 21.21.13.7654 from 2016-12-29). Sound goes through a USB audio device with default driver by Microsoft.

Using these instructions (https://www.kodinerds.net/index.php/Thre…-Simple/), I set up the IPTV Simple Client to receive the RTP streams from “Telekom Entertain”. I am using the “old” Entertain channels because some of the Entertain TV channels are not received. Specifically, I’m testing with rtp://@239.35.10.2:10000. This channel (and others) are received perfectly fine in VLC — as a side note, the playback starts much faster there. In Kodi, the playback runs well until Kodi suddenly crashes (on this channel and on others). To reproduce, I freshly start Kodi, click “TV” in the menu to bring up the TVChannels screen, select the “ZDF” channel and click the small preview to go to fullscreen. Then I wait for about 10-30 minutes — for this reproduction I was doing something else on another virtual Windows desktop, so I for sure didn’t touch the Kodi window. But it equally crashes when I watch actively.

Here’s what VLC knows about the stream:
Video (256) H264 – MPEG-4 AVC (part 10) (h264); 1280×738; 50Hz; Planar 4:2:0 YUV
Audio (257) A52 Audio (aka AC3) (a52), stereo, 48000 Hz, 384 kB/s
Audio (258) MPEG Audio layer 1/2 (mpga)
Subtitles (259) Teletext (telx)

The Visual Studio debugger says: An unhandled win32 exception occured in kodi.exe [5620].
“Ausnahmefehler bei 0x779EFF33 (ntdll.dll) in kodi.exe: 0xC0000005: Zugriffsverletzung beim Schreiben an Position 0x0000001C”
(roughly “Exception at 0x779EFF33 (ntdll.dll) in kodi.exe: 0xC0000005: Access violation when writing at position0x0000001C”)

The debug log is 68M and can’t be uploaded anywhere that I know of. I tried to extract the relevant bits: http://pastebin.com/GJBsxFDk this is the head, then it goes on and on like this (a typical second of log output) http://pastebin.com/0yDsLhNS and then it crashes (presumably around 17:19:18.660, though similar errors occur before) http://pastebin.com/0yiiF9SQ
I also get a stack trace: http://pastebin.com/UkY1r0xr and a 300K dump.

Any help is appreciated.

Best,
Philipp