Kernel/kodi/LibreELEC crash

    I installed LibreELEC 9.0.2 and the system have crashed now few times. This are the logfiles:

    dmesg from the crash this day:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Kodi crash log from few days ago:

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Kodi 18.3 will have a fix for a memory leak that occurred when VAAPI or VDPAU hw acceleration was used. Wait for 9.0.3, it should be out very soon.

    It is possible. The only useful info that I see in log files is this:

    Code
    [ 4141.470827] Out of memory: Kill process 709 (kodi.bin) score 852 or sacrifice child
[ 4141.470868] Killed process 709 (kodi.bin) total-vm:4562004kB, anon-rss:3181944kB, file-rss:0kB, shmem-rss:8kB

    This is from the first logfile. The second logfile i post is some days older and a different crash reason. Is it? Thats the question. Why have it crashed some days ago and create such a kodi crash file? The first logfile was the dmesg output from today(and not from few days ago when the other crash happened).

    3181944kB kodi.bin RSS size in 4141 seconds (from dmesg) is unlikely for the found slow growing memory leak.

    In the crash log there are a lot of

    Code
    2019-06-15 21:10:02.489 T:139781078423296  NOTICE: VAAPI::Close
2019-06-15 21:10:02.489 T:139780029404928  NOTICE: COutput::OnExit: Output Thread terminated
2019-06-15 21:10:02.494 T:139780029404928  NOTICE: COutput::OnStartup: Output Thread created

    at the end before crashing in

    Code
    Thread 1 (Thread 0x7f2151869700 (LWP 976)):
#0  0x00007f2168678661 in vaDestroyContext () from /usr/lib/libva.so.2
#1  0x00007f216781bf0c in ?? () from /usr/lib/libavcodec.so.58
#2  0x00007f216745a88a in ?? () from /usr/lib/libavcodec.so.58
#3  0x00007f216753c705 in ?? () from /usr/lib/libavcodec.so.58
#4  0x00007f216753d551 in ?? () from /usr/lib/libavcodec.so.58
[...]

    Looks like "something" fails an then run out of resources. ;)

    Updated mesa and/or kernel driver may help on your hardware but there is no guaranty.