April update causes System freezes

I went the other way and am testing OSMC Krypton builds from here OSMC test builds for Krypton 17 (continued) currently running:

16.8-079, 12 May 2016: Based off OSMC commit 49be9df and newclock5 (f6975caf)

I really wanted to stay with OSMC, I do not like not having mainstream linux under the hood.

Problem does not seem to occur it was simply an upgrade from 16.1 Jarvis following instructions in the Krypton post. It had all the addons we use before upgrade which seem to work with the latest build. Aeon Nox skin had to upgraded via zip to latest 5.9.0 that has Krypton support. Other than that

Our main use is playing NAS media and watching LiveTV from MythTV Server, some YouTube occasional IPlayer. I appreciate that these builds will likely be unstable but was curious if the latest core code would have the issue.

Cheers
Spart

Okay, thatā€™s interesting information. Good news for going forward, although it would still be useful to get to the bottom of the Jarvis issue.

I haveā€™nt seen any issues, since it last froze when I have deactivated the debug logging while Video playback was active.
My Samba Server was uninstalled long before the Problem even First occured, so no confirmation on that front here.

I realise my post Music playback crash in May update - #3 by amos

is likely the same as this one, consisting of the same COMX errors. Logs in that post.

It seems this is largely reproducible on my Pi3 on May update, I tested it in the context of music playing and video. The crash happens in two stages. First the music hangs, but the UI is still traversable. Then I attempt to interact with the player in any way, the whole system hangs, requiring a kodi reboot.

The following produces it: Set music playing. Then hit down to cycle quickly through all the artist thumbnails. However even slow traversal can create the problem, and indeed a music playing hang has occurred while not interacting with the system, but that is harder to reproduce. It is always associated with errors of the form

ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.egl_render wait event timeout
18:11:39 101183.656250 T:1498276848
ERROR: COMXTexture::Decode m_omx_egl_render.WaitForOutputDone result(0x80001011)

sometime after something like

DEBUG: COMXCoreComponent::Initialize OMX.b
roadcom.egl_render input port 220 output port 221 m_handle 0x5193dbe8
18:11:37 101181.656250 T:1294455792 DEBUG: COMXCoreComponent::Deinitialize : O
MX.broadcom.egl_render handle 0x50ef4c30
18:11:37 101181.656250 T:1294455792 DEBUG: DecodeJpegToTexture: decoded specia
l://masterprofile/Thumbnails/e/ebbea169.jpg 200x197
18:11:37 101181.656250 T:1498276848 DEBUG: COMXCoreComponent::UseEGLImage comp
onent(OMX.broadcom.egl_render) - port(221), nBufferCountMin(1), nBufferCountActu
al(1), nBufferSize(15360) nBufferAlignmen(16)

AFAICS there is no consistency in the particular thumbnail being
rendered across different crashes unless I am misreading the log. Certainly there is no consistency in the thumbnail being displayed at the time of the music player hang.

This will eventually hang kodi entirely if any attempted play is made or further fast cycling is done.

This was not present in the March build, and is in May. The April I am less sure about simply because I was away/busy much of the month and didnā€™t use it much. All my music etc is on a NAS accessed via NFS. The thumbnails are local. Problem occurs on both Pi2 and Pi3. I have been using this system for a long while without problems previously.

@popcornmix after a few days of testing the Kodi Krypton builds specifically the 079 build. I have experienced the problem twice. A lot less than on the Jarvis builds but nevertheless still there.

Cheers
Spart

A debug log from Krypton would be useful just to confirm if it the same issue or something else.

@popcornmix I will try but the log files can get huge pretty quick and the problem seems to be less prevalent (a couple of days) on the Krypton builds.

Cheers
Spart

A non-debug log after the failure is better than nothing - it may give some info about the failure.

Wilco.

I had to Google what that meantā€¦

1 Like

FOFL !!!

@popcornmix @sam_nazarko

OK problem just occured. Symptom is after exiting a playing TV episode and returning to he TV show list no TV show banners are displayed UI is non responsive. At this point I have run grab-logs from an ssh session.

See PM for details. I have multiple piā€™s with the same issue, overclock, addons, third party skin etc. seem to make no difference as the problem occurs on a standard current build and latest Krypton builds with standard skin and no addons.

Cheers
Spart

Are they all Pi1 devices?

You should put gpu_mem back to 144 - 256 is a bit high for a 512M Pi 1 and may cause memory issues on the arm side.

EDIT: I note the file you were playing was MSMPEG4V3 - something that needs to be software decoded.
Does the problem occur more often following a software decoded file, compared to a hardware decoded one?

Iā€™m having the issue described here too. Since the april update, may update didnā€™t solve

RPi B+, library is on a NTFS external USB driver, externally powered
Using Aeon Nox 5.7.3 as a skin

I can use Kodi normally, I can see HD TV shows without issues, but often (2nd episode normally) fanarts go stuck and canā€™t load anymore, and if I try to launch an other video, Kodi hangs loading it. The system is still responsive, I can ask to reboot, and normally it fixes it.

Iā€™ve tried to upgrade the skin, but it hanged with a black screen, and I had this in the log (i was tailing):

20:00:57 13884.911133 T:3003118576  NOTICE: CAESinkPi:AddPackets Underrun (delay:0.00 frames:2205)
20:03:02 14009.901367 T:2531259376 WARNING: COMXImageFile::GetCodingType progressive images not supported by decoder
20:03:02 14009.907227 T:2531259376  NOTICE: LoadJpeg: unable to load /home/osmc/.kodi/addons/skin.aeon.nox.5/fanart.jpg
20:03:33 14041.619141 T:3023430576 WARNING: Cleanup: Having to cleanup texture pointer_arrow.png
20:03:33 14041.630859 T:3023430576 WARNING: Cleanup: Having to cleanup texture pointer_click.png
20:04:22 14090.128906 T:2702177264  NOTICE: ES: Client  from 192.168.1.100 timed out

Are the JPEG still the culprits?

Hello,

It seems I have this issue too running on rpi 3 B.

My logs are here

02:21:32 391056.500000 T:1180689392 NOTICE: [plugin.audio.soundcloud] Running: SoundCloud (2.0.5) on Jā€¦ (16.1) with Python (2.7.9)
02:21:40 391064.312500 T:1222632432 NOTICE: Previous line repeats 1 times.
02:21:40 391064.312500 T:1222632432 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.egl_render wait event timeout
02:21:40 391064.312500 T:1222632432 ERROR: COMXTexture::Decode m_omx_egl_render.WaitForOutputDone result(0x80001011)
02:21:40 391064.312500 T:1222632432 NOTICE: DecodeJpegToTexture: unable to decode to texture special://masterprofile/Thumbnails/6/6686bf8b.jpg 300x300

It happens after at least 15 hours being powered on, and mainly when Iā€™m in soundcloud addon, in ā€œFollowingā€ section.

Skin is Amber

@popcornmix No, a mixture of pi 1 B & B+ and Pi 2/3

Had no idea about the MSMPEG4V3 software decoding part!
Cheers
Spart

Put my Pi on debug logging this morning as its freezing all the time and getting really frustrating, left it on all day. Went to use it in the evening and it had froze up so had to ssh in.
File size is large and wouldnā€™t upload log so am sharing from dropbox
https://www.dropbox.com/s/rem43kxmjm99hvw/kodi.old.log?dl=0
Hope this is of any use.

No errors in this log. When it has hung can you report output of dmesg.
Iā€™m interested in ā€œout-of-memoryā€ errors.

Ok will look into that next time

just done the usual fail to load fanart after returning to gui.
dmesg output in ssh doesnt contain any ā€œout-of-memoryā€ errors
is /var/log/dmesg still current location as that hasnt been written to for 2 months and is empty