Kodi "Freezing"

The issue you are currently experiencing with OSMC

This has been happening for a while (months; maybe much longer) now and I’m finally trying to figure out what the cause is. It happened last night while watching something and I just went to sleep, hoping it might finish. What happens is that the UI just gets extremely unresponsive. I can hit an arrow on the remote and it might take anywhere from 30 seconds to 20 minutes for that single button to be acted upon by Kodi. When I woke up, it was still doing this, though my wife said it was briefly working. I suspect Kodi may have rebooted a couple of times overnight and she happened to catch it shortly after a reboot.

What you were doing when this issue occurred

Nothing specific. It can happen while watching a video or starts randomly when no one is even using it.

Whether you can replicate this issue on demand. If you can, then please provide some steps on how an OSMC developer can reproduce the same issue.

I cannot pin down anything that causes this.

The device you are currently running OSMC on

Vero 4K+

What peripherals are attached to the device?

Logitech USB Unifying receiver.

Has this issue been introduced by a new version of OSMC?

No. It has been happening across several updates. It might even go back to v18.8 or earlier.

When did the issue first appear and can you recall a time when it was not present?

Sadly, I don’t know.

I tried to grab the logs, but wound up with the frowny face while it was slowly uploading. Due to the UI, I needed to grab the logs via the command line. What was grabbed before the crash is here: https://paste.osmc.tv/axumiqumeg

In my own troubleshooting, I’ve noticed that every time this happens, ‘top’ shows multiple kodi.bin processes are in a ‘D’ state and memory usage is ~1.4G with at least one CPU showing a lot of activity. I’ve also seen kodi.bin processes showing their running time as up to 36 hours.

My NAS is a Windows 10 VM running under ESXi 6.7u3 and that’s where the fstab entries are pointing to. When this happens, neither the W10 VM nor the ESXi host, itself, show any high disk I/O usage. In fact, they both seem to be quite inactive across CPU, disk, network, and memory. I can even access the shares and play video files back via other computers without lag or other apparent issues, while this is going on.

One other thing that MIGHT be of use to note is that I’m using a MOCA adapter to hardwire the Vero to my network. The Vero plugs into a regular switch and the switch then connects to the network through the MOCA adapter.

Let me know if you see anything in the logs or if you’ll need another set of logs uploaded.

Thanks for your time!


Is this the supplied remote?

Please enable debug logging. I see:

2022-04-16 06:51:02.893 T:2782 ERROR : ActiveAE::InitSink - failed to init


[49242.776373] SLUB: Unable to allocate memory on node -1, gfp=0x2008000(GFP_NOWAIT|__GFP_ZERO)
[49242.776376]   cache: nfsd4_lockowners, object size: 400, buffer size: 400, default order: 1, min order: 0
[49242.776379]   node 0: slabs: 51, objs: 980, free: 0
[49242.776413] LanguageInvoker: page allocation failure: order:0, mode:0x2204000(GFP_NOWAIT|__GFP_COMP|__GFP_NOTRACK)
[49242.776424] CPU: 2 PID: 11962 Comm: LanguageInvoker Tainted: G           O    4.9.113-64-osmc #1
[49242.776425] Hardware name: Vero4KPlus (DT)
[49242.776427] Call trace:
[49242.776435] [ffffff80203f32b0+ 112][<ffffff800908a5b0>] dump_backtrace+0x0/0x214
[49242.776440] [ffffff80203f3320+  32][<ffffff800908a844>] show_stack+0x24/0x30
[49242.776445] [ffffff80203f3340+  48][<ffffff80093d0e58>] dump_stack+0x98/0xc0
[49242.776449] [ffffff80203f3370+ 144][<ffffff8009192560>] warn_alloc+0xfc/0x118
[49242.776454] [ffffff80203f3400+ 320][<ffffff80091930ec>] __alloc_pages_nodemask+0xb00/0xc0c
[49242.776459] [ffffff80203f3540+ 128][<ffffff80091daa58>] new_slab+0x1d8/0x4e0
[49242.776463] [ffffff80203f35c0+ 224][<ffffff80091dc520>] ___slab_alloc.constprop.27+0x258/0x350
[49242.776468] [ffffff80203f36a0+  48][<ffffff80091dc660>] __slab_alloc.isra.21.constprop.26+0x48/0x5c
[49242.776472] [ffffff80203f36d0+  80][<ffffff80091dc73c>] kmem_cache_alloc+0xc8/0x250
[49242.776478] [ffffff80203f3720+  80][<ffffff80093c7ff4>] bfq_get_queue+0xdc/0x244
[49242.776483] [ffffff80203f3770+ 112][<ffffff80093c825c>] bfq_set_request+0x100/0x4c4
[49242.776489] [ffffff80203f37e0+  48][<ffffff80093a2d44>] elv_set_request+0x4c/0x64
[49242.776494] [ffffff80203f3810+ 224][<ffffff80093a7468>] get_request+0x440/0x6a4
[49242.776499] [ffffff80203f38f0+  80][<ffffff80093aa020>] blk_queue_bio+0x8c/0x360
[49242.776504] [ffffff80203f3940+  80][<ffffff80093a7fc0>] generic_make_request+0xc4/0x1e0
[49242.776508] [ffffff80203f3990+  96][<ffffff80093a820c>] submit_bio+0x130/0x17c
[49242.776515] [ffffff80203f39f0+  32][<ffffff80092ca0a8>] ext4_submit_bio_read+0x4c/0x58
[49242.776520] [ffffff80203f3a10+ 256][<ffffff80092ca530>] ext4_mpage_readpages+0x47c/0x600
[49242.776525] [ffffff80203f3b10+  48][<ffffff8009284e18>] ext4_readpages+0x50/0x68
[49242.776530] [ffffff80203f3b40+ 208][<ffffff80091987e4>] __do_page_cache_readahead+0xec/0x240
[49242.776535] [ffffff80203f3c10+ 112][<ffffff800918bd18>] filemap_fault+0x220/0x528
[49242.776540] [ffffff80203f3c80+  48][<ffffff800928e6fc>] ext4_filemap_fault+0x40/0x60
[49242.776546] [ffffff80203f3cb0+ 112][<ffffff80091b9c9c>] __do_fault+0x74/0xec
[49242.776550] [ffffff80203f3d20+ 160][<ffffff80091be070>] handle_mm_fault+0x5dc/0xbf4
[49242.776555] [ffffff80203f3dc0+ 112][<ffffff8009099570>] do_page_fault+0x1fc/0x338
[49242.776560] [ffffff80203f3e30+  48][<ffffff8009099700>] do_translation_fault+0x54/0x70
[49242.776564] [ffffff80203f3e60+  48][<ffffff80090812a8>] do_mem_abort+0x54/0x94
[49242.776567] Exception stack(0xffffff80203f3e70 to 0xffffff80203f3fa0)



I’m seeing a bunch of this stuff that seems to be slowing things down. I’m assuming one of your add-ons is to blame but I don’t know which one…

<general>: UpdateDetailsForMovie: Starting updates for movie 4415

I also see that you have an extrafanart folder set to a mount that is not working and that may be something to look into.

There is also a bunch of MySQL errors in that log.

I want to apologize for not coming back to reply to you both for the assistance. We had a house built and moved to another state, so things got a bit crazy this year. We’re still unpacking, but have made progress and I finally have my Veros set up again. Assuming the issue is still happening, I’ll revisit this in the near future.

No problem – life gets busy. Good luck with the move and let us know how you get on.

I have a similar situation.
Vero 4k+
Hardwired to Ethernet
Stock remote
Files are on a synology device.
MariaDB for video info

Randomly the UI becomes very unresponsive.
Will be browsing the UI when suddenly button clicks stop responding.
Click various buttons X number of times.
Nothing happens
30seconds to 5minutes (or more), the queued button presses suddenly seem to all fire very quickly one after another.
Pressing buttons after this this repeats the same 30sec to 5min delay followed by rapid completion of all button presses.

I have very few addons (I have disabled and uninstalled the majority trying to narrow the cause of this issue. )

This happens randomly. Sometimes it occurs shortly after booting. Sometimes the vero can run for days and days without it happening.

Sometimes when this occurs, while kodi is not responding it crashes to the frowny face and restarts.

This does NOT occur when a video is playing. If a video is playing, it will play and work fine. The issue ONLY occurs when clicking around menus. Could be any menu, browsing movies, looking at movie info, pulling up a trailer for a movie, looking at settings, etc.

What do you need from me if someone were to look into this issue?


Some logs - the original user hasn’t come back so we consider it fixed

Finally got back to trying to troubleshoot this. I don’t believe it’s OSMC’s fault, however. I disabled all my addons and started adding them back a few at a time. As soon as I enabled the skin helper addons, the freezing returned. I suspect it’s the skin helper widget addon, but won’t know until I give it a few days to test. If so, it’s obviously not the fault of OSMC, so I’ll post on Kodi’s forums and mark this as resolved here.