Hello,
after Update to 17.8-176 kodi isn’t crashing anymore how P.H. has written.
Now we have an other Bug:
12:55:40.203 T:833602288 NOTICE: Finding audio codec for: 86018
12:55:40.205 T:833602288 NOTICE: Creating audio thread
12:55:40.212 T:1156313840 NOTICE: running thread: CVideoPlayerAudio::Process()
12:55:40.284 T:1156313840 NOTICE: Creating audio stream (codec id: 86018, channels: 2, sample rate: 48000, no pass-through)
12:55:40.393 T:850379504 ERROR: CMMALRenderer::CheckConfigurationVout Failed to commit vout input format (status=3 EINVAL)
12:55:40.393 T:850379504 ERROR: CMMALRenderer::Run - Failed to send omvb:0x43303998 mmal:0x47eddeb0 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.207 T:850379504 ERROR: CMMALRenderer::Run - Failed to send omvb:0x6176f058 mmal:0x47ede088 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.271 T:783270640 ERROR: CMMALRenderer::Process - Failed to send omvb:0x435d1598 mmal:0x47ede260 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.304 T:783270640 ERROR: CMMALRenderer::Process - Failed to send omvb:0x715a1bd0 mmal:0x47ede438 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.354 T:783270640 ERROR: CMMALRenderer::Process - Failed to send omvb:0x6ac555b0 mmal:0x47ede610 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.387 T:783270640 ERROR: CMMALRenderer::Process - Failed to send omvb:0x4351a460 mmal:0x47ede7e8 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
12:55:41.421 T:783270640 ERROR: CMMALRenderer::Process - Failed to send omvb:0x65ffcbb8 mmal:0x47ede9c0 to vc.ril.video_render:in:0(I42S) (status=03 EINVAL)
…
…
…
12:55:42.426 T:1340617456 ERROR: CMMALPool::GetBuffer - failed pool:0x6c3acc20 omvb:(nil) mmal:(nil) timeout:500
12:55:42.426 T:1340617456 ERROR: CAddonVideoCodec::GetFrameBuffer Failed to allocate buffer
After that the Videosignal get lost and picture remains black.
I’ve found with this error message this thread:
https://forum.kodi.tv/printthread.php?tid=298461&page=149
where popcornmix wrote it could be a bug in firmware.
I hope this helps finding the Problem.
Regards Tobias