I may have spoken too soon - looks like there’s an aggressive memory leak, I can only guess it’s one of the Amlogic drivers since it’s in kernel space.
I’ll try to get some slab debug info if I can work out how to modify kernel params on CE, but looks like something is constantly calling kmalloc and never freeing the memory.
This is already fixed since a few weeks.
Oh, I installed from Oowow a couple days ago and thought that would be the latest nightly. Update notification came through when I powered up today and memory is now looking nice and flat, kmods for docker are in too, thanks muchly 
UHD content does appear to flicker and hitch every few seconds after updating to the latest build, is this a known issue? Can provide logs if that would be useful.
ETA: The hitching wasn’t present on the previous build.
Hitching is fixed in 20221112
just seen the new build was available, only a quick test but so far looking good, not a daily driver though yet as will miss Atmos to much
This is likely related to the currently dodgy audio driver (and would be less an issue once pass-through works), but just in case there’s anything I can try - when connected to my receiver (Denon AVR-X1700H) only 2ch LPCM works. When Kodi tries to send > 2ch LPCM to the receiver, the AVR displays unknown format and no audio is received.
If I connect the VIM4 to my TV (Sony XR-77A80J) and have the LPCM sent through the TV to the receiver via eARC, I can get > 2ch audio, but A/V sync is much more reliable the other way around. The receiever plays LPCM from other sources fine (I have an older x86 Kodi box with regular HDA audio that works no problem).
The upload with full logs option appears to be broken on 20221117 (consistently fails and says to retry), but I can upload the Kodi logs separately if required - there doesn’t seem to be anything super-interesting in them though, Kodi is sending the right channel counts/bit-depths/etc to the audio codec for output. Below are the configs/debug-info when connected to each of the two devices. Other than failing to detect DV compatibility when connected to the TV (and missing HDR10+ on the receiver), I don’t see much in the way of significantly different between the two:
Receiver: http://ix.io/4gia
TV: http://ix.io/4gib
Has someone working on “12:01” bug? What I’m talking about: When playing local MP4 video, Kodi freeze on “12:01” time and only seeking forward can resume normal playback. You can check this yourself - no logs needed from other people.
Unable to replicate with City Lights (1931).mp4 see: http://ix.io/4gSY
Unless you have something to hide, provide logs. No logs, no problem, meaning no need for us to get involved.
You sure your MP4 isn’t corrupt?
Can you suggest me how to check if MP4 file is correct (under Linux or Windows)?
Hm… After the recent updates, there no sign of this “12:01” bug, for now. Just some videos can’t even open successfully (some of them plays without sound), but this can be Kodi related or Amlogic binary blob issues. Clearly, it needs more time.
If you read the thread you’ll see there are issues with the audio driver - particularly, passthrough of HBR audio is broken, workaround is to use LPCM, though that has some issues too…
This LPCM issue is resolved in the latest release <3
Does the Vim1s suffer from the same memory leak? I just bought one and it freezes. Similar to the Vim4.
That particular memory leak was resolved a long time ago.
Currently there was no memory leak but the kodi didn’t restart and the system got reset.
Anyway, it should be solved with latest nightly.
Any news about VIM4 nvme support yet?
Nothing changed in this area (I don’t have any drive to test).
About | FAQ | Terms of Service | Privacy Policy | Legal Notice