Vero 4K+ - Kodi 19.1 - Kodi exited with return code 137

Help and Support Vero 4K / Vero 4K +
1

Dear OSMC Community,

Since I’ve ran the latest update, I’m facing an issue where the graphical interface crash in a sad face very often. Could be after 2 minutes of use or 30 minutes of use. it happens mainly when navigating in the menu or only having the library getting updated.

I’ve uploaded the full log of the Kodi that can be found here :
https://paste.osmc.tv/azinabifed

Here’s a log from yesterday where the issue happened many times : https://paste.osmc.tv/qasinokofi

I had a quick look and here’s what I found :

Aug 17 09:43:05 Shiriu kernel: Out of memory: Kill process 2578 (kodi.bin) score 569 or sacrifice child
Aug 17 09:43:05 Shiriu kernel: Killed process 2578 (kodi.bin) total-vm:2103884kB, anon-rss:1156380kB, file-rss:1852kB, shmem-rss:0kB
Aug 17 09:43:05 Shiriu sudo[2572]: pam_unix(sudo:session): session closed for user osmc
Aug 17 09:43:05 Shiriu mediacenter[2377]: /usr/bin/mediacenter: line 212:  2572 Killed                  sudo -u osmc MALLOC_MMAP_THRESHOLD_=8192 LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs
Aug 17 09:43:05 Shiriu kernel: oom_reaper: reaped process 2578 (kodi.bin), now anon-rss:4kB, file-rss:0kB, shmem-rss:0kB
Aug 17 09:43:05 Shiriu mediacenter[2377]: Kodi exited with return code 137 after 15 hours, 10 minutes and 58 seconds

The Vero states that there is no more memory available.

So I went to the System Info Menu and look at the “Memory used” which is constently around 20% when updating the library.
If I start browsing between the Movies, this number will reach around 30%.
Once, I saw the percents grow suddenly and super fast to 100% and then crash to the sad face.
I would see the login prompt on the tv for a minute and the gui would relaunch itself.

I’ve tried to recreate the .kodi user folder but the issue remains.

Also, sometimes, more often now, the osmc will just crash to nothing.
There are no signal on the TV.
It does respond to ping, I reach the login screen with SSH, but when I connect, I never get a prompt, like this :
image
and then I get a timeout after a while.
It takes multiple reboots to get it to work normally again.

Would you have any idea what the issue could be ?

There are no external devices plugged to the Vero.
There is only HDMI, optical, network cable and power cord.

Share are mounted via the fstab file and Library are set with the /mnt/folder path.

It has always been updated from past version to the newer ones.
I’d like to avoid reinstalling a fresh 19.1, but I can try as well.

Thanks so much !

MathFly_

1 Like
2

Ok, I ended up reinstalling the Vero.
I’m now re-scanning the libraries.

I’ll let you know if it is better !

Thanks !

3

Hi. I have similar issue first after upgrade And then install from scratch. Both where workin some time but sad face or frozen after for a while. Setup was pure osmc without exra addons. Now back in old release and that ole is working as it shoud.

4

So indeed, even after a fresh reinstallation, and a full library scan, the gui keeps crashing on a sad face when I browse the video library.
Here are the uploaded logs :
https://paste.osmc.tv/ucokaruyey

It does still shows this error :

Aug 17 17:50:01 Shiriu kernel: Out of memory: Kill process 5060 (kodi.bin) score 606 or sacrifice child
Aug 17 17:50:01 Shiriu kernel: Killed process 5060 (kodi.bin) total-vm:2060008kB, anon-rss:1232596kB, file-rss:0kB, shmem-rss:0kB
Aug 17 17:50:01 Shiriu kernel: oom_reaper: reaped process 5060 (kodi.bin), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Aug 17 17:50:01 Shiriu kernel: fb: osd_release now.index=0,open_count=1
Aug 17 17:50:01 Shiriu sudo[5059]: pam_unix(sudo:session): session closed for user osmc
Aug 17 17:50:01 Shiriu mediacenter[2383]: /usr/bin/mediacenter: line 212:  5059 Killed                  sudo -u osmc MALLOC_MMAP_THRESHOLD_=8192 LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs
Aug 17 17:50:01 Shiriu mediacenter[2383]: Kodi exited with return code 137 after 0 hours, 0 minutes and 43 seconds

There are no weird addons installed, just the Skin Shortcuts the main page modification and the weather addon.

And the setup is very simple :

  • an NFS share added to the fstab file that points to a share hosted on a Synology NAS (DSM 7.0)
  • cron installed with, in crontab -e, a command to update the library at 7:00 ( * 7 * * * /usr/bin/xbmc-send -a “UpdateLibrary(video)” >> /dev/null 2>&1)
  • 3 video library, one for movie, one for Series and one for Anime (set as TV Shows)

What I’ve noticed with the fresh install is that when the library scan is done for a library, it would not be complete. I’ll try to explain, for example a 4 season serie would be identified with the title, but with 0 seasons and 0 episodes. on the next scan, it might find the actual seasons. Or sometimes, it will only index 2 seasons and a half.

Can you please advise on what to do here as the Vero 4K+ is not usable, even after a fresh install.

In the meantime as mika.m.nummela suggested, I might just reinstall the previous version.

Thanks for support.

MathFly_

5

Ok, It’s getting worst.
I’ve reinstalled november update, went through the basic install steps.
Done the same:

  • Mount NFS Share from Synology NAS (DSM7.0) in /etc/fstab with this line : 192.168.1.250:/volume1/Videos /mnt/Videos nfs noauto,x-systemd.automount 0 0
  • installed weather addon
  • installed cron with a crontab -e : * 6 * * * /usr/bin/xbmc-send -a “UpdateLibrary(video)” >> /dev/null 2>&1
  • Added the 3 libraries from root folder then /mnt/Video and the folder name and selected that data should not be updated right away.

Now, 30 seconds after I start the library update, the Vero 4K+ just crash.
No TV signal, not reachabe via ping or SSH.
Nothing.

I have to pull out the power cord two or three times to have it working again.

I’ve tried todisable the fstab mount and set the Library path to NFS Share instead of the /mnt/video.

This setup has been working since I got my Vero 4K+ when it was released.
Now it’s getting ridiculous as I cannot even start a Library scan.

I’ve updated the logs here : https://paste.osmc.tv/etegerizeb

Thanks for support

6

So after some more testing, it keep crashing when browsing the local libraries (Movies & TV Shows). when this happen, it is not reachable at all on the network and won’t give any display.
It gets me multiple times to pull out the power cord and put it back to get a regular boot
Multiple times, it will show “Please Standby”, then would not start.
The same, no display and not reachable on the network (ping & SSH).

@sam_nazarko
Could it be an hardware issue ? Is there an easy way to test the memory and/or the internal drive ?

I’ve updated an updated log here : https://paste.osmc.tv/iqofoyelus

What would be the next troubleshooting steps ?

Thanks !

7

Alright, more testing.
So last month, I’ve put a bit higher the shelf were the Vero 4K is located. for me there was way enough space for air to circulate in the shelf (It’s an open shelf, there is around 10 cm of height and plenty space behind and on each side).
Yesterday, I’ve moved the Vero on another shelf where there are more space available.
It seems that the problem does not occurs since I moved it.

Could it be that all of this is happening because of an heating problem ?

I’ve reinstalled version 19.1 and it seems to work fine as well.

I’ll keep testing tonight and will let you know the results.

Cheers,

8

Possible, while I have not seen an increase of heat on my Vero4k since moving to v19

9

When I look at the Temperature in System Info → Hardware, it goes from 70°C to 82°C now, which I think is a normal behavior.
I cannot tell when it was crashing as it’s happening when I was navigating the Library and the temperature variable is not shown in the onscreen debug log.
I’ve read in another forum thread that the Vero would shutdown around 120°C, I don’t think that it has reached this temperature.

10

My idle temps are around 64-66°C

11

70 → 80 has been mesured while the device scans a Library.
I’ll check when I’m back home what is the idle temperature.

12

So I checked yesterday when I came back home.
When I turned on the TV, temp was at 55°C in the new location.
when I started indexing the movies that were not recognized by the initial scan and browsing through the Library, it reached 80° C.
But it stayed stable.

I’m not sure what happened here, but moving it definitely made thing better has it did not crash and worked just fine when I indexed around 20 movies and then browse the whole Library.

I used to use fstab, but for the tests, i’ve set the Libraries to simple nfs:// shares
With the simple shares, I faced some buffering issues for 4K BD files (around 60GB).
Yesterday, I’ve setup autofs and path substitution, it has no more buffering issues and is still rocking :slight_smile:

I’ll keep an eye for some time and see how it goes.

13

So, I spoke too fast.

GUI is still crashing while browsing the movie Library.

I’ve uplaeded the logs here : https://paste.osmc.tv/obaqoxesih

It states the same :

Aug 19 18:14:43 Shiriu kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Aug 19 18:14:43 Shiriu kernel: 2446 total pagecache pages
Aug 19 18:14:43 Shiriu kernel: 0 pages in swap cache
Aug 19 18:14:43 Shiriu kernel: Swap cache stats: add 0, delete 0, find 0/0
Aug 19 18:14:43 Shiriu kernel: Free swap  = 0kB
Aug 19 18:14:43 Shiriu kernel: Total swap = 0kB
Aug 19 18:14:43 Shiriu kernel: 524032 pages RAM
Aug 19 18:14:43 Shiriu kernel: 0 pages HighMem/MovableOnly
Aug 19 18:14:43 Shiriu kernel: 14711 pages reserved
Aug 19 18:14:43 Shiriu kernel: 161792 pages cma reserved
Aug 19 18:14:43 Shiriu kernel: [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
Aug 19 18:14:43 Shiriu kernel: [ 2156]     0  2156     4712     1775      30       2        0             0 systemd-journal
Aug 19 18:14:43 Shiriu kernel: [ 2182]   106  2182     1342       80       7       2        0             0 rpcbind
Aug 19 18:14:43 Shiriu kernel: [ 2188]     0  2188     3998      219      10       2        0         -1000 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [ 2320]     0  2320     2728       25       6       2        0             0 apploader
Aug 19 18:14:43 Shiriu kernel: [ 2323]     0  2323     2756      195       9       2        0             0 systemd-logind
Aug 19 18:14:43 Shiriu kernel: [ 2324]   108  2324     1279       89       7       2        0             0 avahi-daemon
Aug 19 18:14:43 Shiriu kernel: [ 2329]   104  2329     1476      174       6       2        0          -900 dbus-daemon
Aug 19 18:14:43 Shiriu kernel: [ 2336]     0  2336     1437       66       7       2        0             0 bluetoothd
Aug 19 18:14:43 Shiriu kernel: [ 2337]     0  2337     2181      102       8       2        0             0 wpa_supplicant
Aug 19 18:14:43 Shiriu kernel: [ 2338]     0  2338      460       19       5       2        0             0 eventlircd
Aug 19 18:14:43 Shiriu kernel: [ 2343]   108  2343     1247       69       6       2        0             0 avahi-daemon
Aug 19 18:14:43 Shiriu kernel: [ 2351]     0  2351     1005       75       6       2        0             0 lircd
Aug 19 18:14:43 Shiriu kernel: [ 2353]     0  2353     2695      151       9       2        0             0 connmand
Aug 19 18:14:43 Shiriu kernel: [ 2356]     0  2356     6421       88       9       2        0             0 bluealsa
Aug 19 18:14:43 Shiriu kernel: [ 2363]     0  2363     1191       54       5       2        0             0 cron
Aug 19 18:14:43 Shiriu kernel: [ 2367]     0  2367     1181       93       7       2        0             0 mediacenter
Aug 19 18:14:43 Shiriu kernel: [ 2410]     0  2410      904       30       5       2        0             0 agetty
Aug 19 18:14:43 Shiriu kernel: [ 2442]     0  2442    12947      154      15       2        0             0 automount
Aug 19 18:14:43 Shiriu kernel: [ 2443]  1000  2443     2045      132       8       2        0             0 udisks-glue
Aug 19 18:14:43 Shiriu kernel: [ 2447]     0  2447     2264      165       8       2        0         -1000 sshd
Aug 19 18:14:43 Shiriu kernel: [ 2468]     0  2468     6831      182      12       2        0             0 udisks-daemon
Aug 19 18:14:43 Shiriu kernel: [ 2476]     0  2476     2150       93       9       2        0             0 udisks-daemon
Aug 19 18:14:43 Shiriu kernel: [ 2503]     0  2503     9107      211      12       2        0             0 polkitd
Aug 19 18:14:43 Shiriu kernel: [ 2675]     0  2675     1251       45       6       2        0             0 bluealsa-aplay
Aug 19 18:14:43 Shiriu kernel: [13418]     0 13418     1692      125       7       2        0             0 sudo
Aug 19 18:14:43 Shiriu kernel: [13419]  1000 13419   528466   310424     774       3        0             0 kodi.bin
Aug 19 18:14:43 Shiriu kernel: [13696]     0 13696     3998      223       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13697]     0 13697     3998      223       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13698]     0 13698     3998      223       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13699]     0 13699     3998      223       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13700]     0 13700     3998      207       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13701]     0 13701     3998      207       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: [13702]     0 13702     3998      207       8       2        0             0 systemd-udevd
Aug 19 18:14:43 Shiriu kernel: Out of memory: Kill process 13419 (kodi.bin) score 611 or sacrifice child
Aug 19 18:14:43 Shiriu kernel: Killed process 13419 (kodi.bin) total-vm:2113864kB, anon-rss:1241340kB, file-rss:356kB, shmem-rss:0kB
Aug 19 18:14:43 Shiriu kernel: oom_reaper: reaped process 13419 (kodi.bin), now anon-rss:4kB, file-rss:0kB, shmem-rss:0kB
Aug 19 18:14:43 Shiriu kernel: fb: osd_release now.index=0,open_count=1
Aug 19 18:14:43 Shiriu sudo[13418]: pam_unix(sudo:session): session closed for user osmc
Aug 19 18:14:43 Shiriu mediacenter[2367]: /usr/bin/mediacenter: line 212: 13418 Killed                  sudo -u osmc MALLOC_MMAP_THRESHOLD_=8192 LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs
Aug 19 18:14:43 Shiriu mediacenter[2367]: Kodi exited with return code 137 after 0 hours, 2 minutes and 25 seconds

Does anyone has any idea on what it could be ?

I’ve checked the temperature, it’s running at 60°C at the time of the crashs.

14

I could record a video where you clearely see the memory going up and then the GUI crashing.
It happenend when I was in the System Info Menu, I didn’t browse or anything…

You can check the video here : - YouTube

Here are the logs taken after the video was recorded : https://paste.osmc.tv/owagatobar

Could anyone help with this please ?

Thanks !

15

The problem is clear:

Aug 19 18:14:43 Shiriu kernel: Out of memory: Kill process 13419 (kodi.bin) score 611 or sacrifice child

Kodi is crashing because your device is running out of memory.
Have you customised advancedsettings.xml at all (perhaps changing the buffer size) or have a large EPG (IPTV) or a large number of add-ons active?

16

@sam_nazarko
Hey Sam,
Yes, I know that, the only thing is I don’t know why it goes out of memory as nothing is running at the time of the crash. It happens mainly when I browse the Library.
If you check the youtube video. I strictly do nothing, I just stay on the Hardware info screen.

I’ve created and advancedsettings.xml file, but with only path substitution.
Here is the content of the file :

<?xml version="1.0" encoding="utf-8"?>
<advancedsettings>
 <pathsubstitution>
  <substitute>
    <from>nfs://192.168.1.250/volume1/Videos/</from>
    <to>/mnt/Videos/</to>
  </substitute>
 </pathsubstitution>
</advancedsettings>

It’s a very basic install, no IPTV, and the only addons installes are the Skin Shortcut to modify the main screen.
That’s all.

I’ve setup autofs after adding the library as nfs://, so that’s why I did set path substitution.

Could it be this that consume the memory ?

Thanks !

17

It’s possible. What happens if you disable autofs?

18

@sam_nazarko

This morning it was crashed again, I had to pull the plug two or three times to have it working.

I’ve commented the line added in the /etc/auto.nfs.shares and renamed the advancedsettings.xml, then reboot.
I’ve also checked “Wait for Network”. in the wired connection settings.
So far, I cannot reproduce the issue.

But I have buffering issues with larger files that I do not not face when fstab or autofs is used to mount the shares.

I’ll test tomorrow to activate autofs and remap the Library to /mnt/Videos instead of using the advancedsettings.xml for path susbtitution.
Tho from what I’ve tested before, I faced the issue with fstab as well, without advancedsettings.xml file.

I’ve also restarted the switch the NAS and the Vero are connected to. It’s a simple 8 port Netgear.

19

OK, I’ve tested again with autofs and set the Library to use /mnt/Videos without path substitution.
The issue is the same, when scanning the library or browsing, Kodi error 137, out of memory.

While the Library is setup with nfs://192.168.1.250/Videos/, it does not happen.

Do you know why it would cause such issues with autofs or fstab mount ?

The thing is that, I don’t mind using the nfs:// share, but I face some buffering issues on larger files as a 40 - 50 Gb 2160p movie.
I don’t face this issue when autofs or fstab is used.

I’ve successfully used fstab since I have my Vero 4K+ and it never caused any issues.

Thanks for support !

20

Can you show us how autofs is configured?
I wonder if there’s some over-aggressive buffering causing this

Sam