Login at Kodi Home

**garbear** · (This post was last modified: 2018-03-05, 22:02 by garbear.)

(2018-03-03, 20:35)trihy Wrote: Xbox 360 controller back button is still bad mapped.

It should get you to home. And does nothing. Also start button does some weird stuff. Not sure to which or what is maped.

Kodi has a system for mapping controllers to Kodi actions. Check out https://kodi.wiki/view/HOW-TO:Modify_joystick.xml . What actions are your back and start button mapped to?

**garbear** · (This post was last modified: 2018-03-05, 22:07 by garbear.)

New builds posted! Windows is fixed!

(2018-03-05, 19:22)Julipo Wrote: It seems that RetroPlayer is something to use remotes or controllers easily

That's the goal! Once we import the RetroArch joystick configs and the emulator button maps from the controller topology project, we should have close to 100% controller coverage for all emulators on all platforms.

(2018-03-05, 20:49)linkinsoldier Wrote: Well the question is: are they not allowed to advertise it or are the saving the big bang for the last official release note

Good question Smile

Powerhouse · 2018-03-06, 01:34

Garbear, you rock!

Been waiting for a Windows fix for what seems forever (not really, but feels like it).

Wintermute0110 · 2018-03-06, 10:47

Garbear,

Advanced Emulator Launcher already supports Retroplayer natively and I believe it works without issues in Leia. Now that Leia Alpha 1 is out, shortly I will make AEL both a program and games addon so it will show up in both sections.

I also want to add Retroplayer support for Advanced MAME Launcher. Currently, I extract MAME XML by calling the MAME executable the user has installed (external emu). In order for AML to support Retroplayer, I will need the XML with the machine and ROM info each MAME core supports. Is there a way to generate those XMLs in Retroplayer?

Also, about the Software Lists: does any of the MAME cores also support Software Lists?

Thanks a lot for your help.

xodi · 2018-03-06, 18:19

The latest 2018-03-04 arm64 build crashed many times in my Android device, the previous build never crashed, I got the logcat for the crash:

Code:
F/libc    (15607): invalid address or address of corrupt block 0x55a3e4c770 passed to dlfreeF/libc    (15607): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xdeadbaad in tid 23639 (Thread-204927)I/DEBUG   (  171): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***I/DEBUG   (  171): Build fingerprint: 'Amazon/full_sloane/sloane:5.1.1/LVY48F/36.5.8.7_user_587700720:user/release-keys'I/DEBUG   (  171): Revision: '0'I/DEBUG   (  171): ABI: 'arm64'I/DEBUG   (  171): pid: 15607, tid: 23639, oom: 0, name: Thread-204927  >>> org.xbmc.kodi <<<I/DEBUG   (  171): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaadI/DEBUG   (  171): Abort message: 'invalid address or address of corrupt block 0x55a3e4c770 passed to dlfree'I/DEBUG   (  171):     x0   3408b251dc991e56  x1   0000007fa16ab650  x2   0000000000000000  x3   0000000000000000I/DEBUG   (  171):     x4   0000000000000000  x5   00000000deadbaad  x6   0000000000000000  x7   0000000000000010I/DEBUG   (  171):     x8   7f7f7f7f7f7f7f7f  x9   6471656b631f6e73  x10  7f7f7f7f7f7f7f7f  x11  3408b251dc991e56I/DEBUG   (  171):     x12  0000000000000001  x13  3408b251dc991e56  x14  0000000000000043  x15  0000000000000049I/DEBUG   (  171):     x16  0000007fa1467ad0  x17  0000007fa13e9928  x18  0000000000000000  x19  00000055a3e4c770I/DEBUG   (  171):     x20  0000007fa146e000  x21  00000055a3e4c780  x22  0000007fa146ee40  x23  0000007f7adfbee0I/DEBUG   (  171):     x24  0000007f7adfcba0  x25  0000007f87dcf825  x26  0000007f7adfcba0  x27  0000007f848ceba0I/DEBUG   (  171):     x28  0000007f848ceba0  x29  0000007f7adfbda0  x30  0000007fa140d9a4I/DEBUG   (  171):     sp   0000007f7adfbda0  pc   0000007fa140d9ac  pstate 0000000060000000I/DEBUG   (  171):I/DEBUG   (  171): backtrace:I/DEBUG   (  171):     #00 pc 00000000000429ac  /system/lib64/libc.so (dlfree+408)I/DEBUG   (  171):     #01 pc 0000000000017af8  /system/lib64/libc.so (free+20)I/DEBUG   (  171):     #02 pc 0000000000dbcb58  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE10deallocateEv+112)I/DEBUG   (  171):     #03 pc 0000000000dbca8c  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE13__move_assignERS8_NS_17integral_constantIbLb1EEE+24)I/DEBUG   (  171):     #04 pc 0000000000db9354  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN13CVideoInfoTagaSEOS_+284)I/DEBUG   (  171):     #05 pc 0000000001042764  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase14GetEpisodeInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagii+268)I/DEBUG   (  171):     #06 pc 0000000001046e5c  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase13LoadVideoInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagi+64)I/DEBUG   (  171):     #07 pc 0000000001517454  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager15SetCurrentMovieER9CFileItem+380)I/DEBUG   (  171):     #08 pc 0000000001516dc4  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager17SetCurrentItemJobENSt6__ndk110shared_ptrI9CFileItemEE+88)I/DEBUG   (  171):     #09 pc 0000000001519920  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN18CSetCurrentItemJob6DoWorkEv+72)I/DEBUG   (  171):     #10 pc 0000000001135cc4  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN10CJobWorker7ProcessEv+164)I/DEBUG   (  171):     #11 pc 0000000001221530  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread6ActionEv+60)I/DEBUG   (  171):     #12 pc 00000000012209f0  /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread12staticThreadEPv+224)I/DEBUG   (  171):     #13 pc 000000000001d68c  /system/lib64/libc.so (_ZL15__pthread_startPv+52)I/DEBUG   (  171):     #14 pc 00000000000198c4  /system/lib64/libc.so (__start_thread+16)

**garbear** · (This post was last modified: 2018-03-06, 22:52 by garbear.)

(2018-03-06, 18:19)xodi Wrote: The latest 2018-03-04 arm64 build crashed many times in my Android device, the previous build never crashed, I got the logcat for the crash:

Code:
F/libc (15607): invalid address or address of corrupt block 0x55a3e4c770 passed to dlfreeF/libc (15607): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xdeadbaad in tid 23639 (Thread-204927)I/DEBUG ( 171): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***I/DEBUG ( 171): Build fingerprint: 'Amazon/full_sloane/sloane:5.1.1/LVY48F/36.5.8.7_user_587700720:user/release-keys'I/DEBUG ( 171): Revision: '0'I/DEBUG ( 171): ABI: 'arm64'I/DEBUG ( 171): pid: 15607, tid: 23639, oom: 0, name: Thread-204927 >>> org.xbmc.kodi <<<I/DEBUG ( 171): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaadI/DEBUG ( 171): Abort message: 'invalid address or address of corrupt block 0x55a3e4c770 passed to dlfree'I/DEBUG ( 171): x0 3408b251dc991e56 x1 0000007fa16ab650 x2 0000000000000000 x3 0000000000000000I/DEBUG ( 171): x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010I/DEBUG ( 171): x8 7f7f7f7f7f7f7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 3408b251dc991e56I/DEBUG ( 171): x12 0000000000000001 x13 3408b251dc991e56 x14 0000000000000043 x15 0000000000000049I/DEBUG ( 171): x16 0000007fa1467ad0 x17 0000007fa13e9928 x18 0000000000000000 x19 00000055a3e4c770I/DEBUG ( 171): x20 0000007fa146e000 x21 00000055a3e4c780 x22 0000007fa146ee40 x23 0000007f7adfbee0I/DEBUG ( 171): x24 0000007f7adfcba0 x25 0000007f87dcf825 x26 0000007f7adfcba0 x27 0000007f848ceba0I/DEBUG ( 171): x28 0000007f848ceba0 x29 0000007f7adfbda0 x30 0000007fa140d9a4I/DEBUG ( 171): sp 0000007f7adfbda0 pc 0000007fa140d9ac pstate 0000000060000000I/DEBUG ( 171):I/DEBUG ( 171): backtrace:I/DEBUG ( 171): #00 pc 00000000000429ac /system/lib64/libc.so (dlfree+408)I/DEBUG ( 171): #01 pc 0000000000017af8 /system/lib64/libc.so (free+20)I/DEBUG ( 171): #02 pc 0000000000dbcb58 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE10deallocateEv+112)I/DEBUG ( 171): #03 pc 0000000000dbca8c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE13__move_assignERS8_NS_17integral_constantIbLb1EEE+24)I/DEBUG ( 171): #04 pc 0000000000db9354 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN13CVideoInfoTagaSEOS_+284)I/DEBUG ( 171): #05 pc 0000000001042764 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase14GetEpisodeInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagii+268)I/DEBUG ( 171): #06 pc 0000000001046e5c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase13LoadVideoInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagi+64)I/DEBUG ( 171): #07 pc 0000000001517454 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager15SetCurrentMovieER9CFileItem+380)I/DEBUG ( 171): #08 pc 0000000001516dc4 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager17SetCurrentItemJobENSt6__ndk110shared_ptrI9CFileItemEE+88)I/DEBUG ( 171): #09 pc 0000000001519920 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN18CSetCurrentItemJob6DoWorkEv+72)I/DEBUG ( 171): #10 pc 0000000001135cc4 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN10CJobWorker7ProcessEv+164)I/DEBUG ( 171): #11 pc 0000000001221530 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread6ActionEv+60)I/DEBUG ( 171): #12 pc 00000000012209f0 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread12staticThreadEPv+224)I/DEBUG ( 171): #13 pc 000000000001d68c /system/lib64/libc.so (_ZL15__pthread_startPv+52)I/DEBUG ( 171): #14 pc 00000000000198c4 /system/lib64/libc.so (__start_thread+16)

The error is:

invalid address or address of corrupt block 0x55a3e4c770 passed to dlfree

This indicates a DLL is being unloaded. Could this be causing the crash? Can you offer more context as to when Kodi crashes?

The stack trace indicates a crash in the function:

CVideoDatabase::LoadVideoInfo()
CVideoDatabase::GetEpisodeInfo()

I was the last person to touch VideoDatabase.cpp with PR:13443, so maybe they're related.

Can you do some more testing and try to figure out how to reliably reproduce the crashes?[/font]

Powerhouse · 2018-03-06, 23:06

(2018-03-06, 10:47)Wintermute0110 Wrote: Garbear,

Advanced Emulator Launcher already supports Retroplayer natively and I believe it works without issues in Leia. Now that Leia Alpha 1 is out, shortly I will make AEL both a program and games addon so it will show up in both sections.

OMG, so first Retroplayer for Kodi 18 (sans options for artwork, etc), but now with your addon, we get the full package. Plus I read that my favorite skin "Aeon MQ8" (for Leia) also includes AEL support. So 2018 is turning out to be a great year my use of Kodi.

Thanks for all the work you do.

**garbear** · 2018-03-06, 23:54

(2018-03-06, 10:47)Wintermute0110 Wrote: I also want to add Retroplayer support for Advanced MAME Launcher. Currently, I extract MAME XML by calling the MAME executable the user has installed (external emu). In order for AML to support Retroplayer, I will need the XML with the machine and ROM info each MAME core supports. Is there a way to generate those XMLs in Retroplayer?

Nope. Could we distribute the XMLs with the MAME cores? That's what we do for MSX BIOSes.

(2018-03-06, 10:47)Wintermute0110 Wrote: Also, about the Software Lists: does any of the MAME cores also support Software Lists?

You can find out by checking the source: https://github.com/libretro?q=mame

The libretro team might know the answer to this as well.

Julipo · 2018-03-07, 00:02

I deleted my previous Kodi alfa + config and downloaded the last build from here for windows 64... how can I configure the controls in my keyboard? I opened a rom with SNES9x, clik ¿ESC? (I don't remember now) and a menu appeared. I clicked to "Configure controls", and a windows appeared with lots of systems, but the first is "Kodi" with a Xbox 360 image (I supose that this maps RetroPad), I click to the first letter and start mapping "A" "B" "X" "Y" in my Keyboard (I pressed z, x, a, s...)
Finally "OK" but when I click "Enter" (start) it shows the same menu that I opened with "ESC", when I click z or x it goes to Kodi.

**garbear** · 2018-03-07, 00:39

(2018-03-07, 00:02)Julipo Wrote: how can I configure the controls in my keyboard?

Using the keyboard to emulate a controller is broken. For now, if a ROM requires a controller, you can only play it with another controller.

Keyboard control broke with the merge of the Controller Topology Project last month. It will be fixed in the future, though I'm not sure when.

trihy · (This post was last modified: 2018-03-07, 02:11 by trihy.)

(2018-03-05, 22:02)garbear Wrote:
(2018-03-03, 20:35)trihy Wrote: Xbox 360 controller back button is still bad mapped.

It should get you to home. And does nothing. Also start button does some weird stuff. Not sure to which or what is maped.

Kodi has a system for mapping controllers to Kodi actions. Check out https://kodi.wiki/view/HOW-TO:Modify_joystick.xml . What actions are your back and start button mapped to?

Hi. IM using kodi x64 nightlies

<keymap>
<global>
<joystick profile="game.controller.default">
<a>Select</a>
<a holdtime="500">ContextMenu</a>
<b>Back</b>
<x>ContextMenu</x>
<y>FullScreen</y>
<start>ActivateWindow(PlayerControls)</start>
<guide>ActivateWindow(Home)</guide>
<up>Up</up>
<down>Down</down>
<right>Right</right>
<left>Left</left>
<leftthumb>Screenshot</leftthumb>
<rightthumb>ActivateWindow(ShutdownMenu)</rightthumb>
<lefttrigger>ScrollUp</lefttrigger>
<righttrigger>ScrollDown</righttrigger>
<leftbumper>ScrollUp</leftbumper>
<rightbumper>ScrollDown</rightbumper>
<leftstick direction="left">Left</leftstick>
<leftstick direction="right">Right</leftstick>
<leftstick direction="up">Up</leftstick>
<leftstick direction="down">Down</leftstick>
<rightstick direction="left">VolumeDown</rightstick>
<rightstick direction="right">VolumeUp</rightstick>
<rightstick direction="up">VolumeUp</rightstick>
<rightstick direction="down">VolumeDown</rightstick>
</joystick>

I dont see the back button there? They mapped guide button as homescreen, which is pretty good, but on windows it doesnt workk, cause windows take exclusive control of the guide button.

It should return to homescreen like on kodi v17 I think.

I had to add

<back>ActivateWindow(home)</back>

I think start button is weird mapped, but maybe they have some point here. When you hit start on a movie the title blinks and does nothing, maybe they will add some functionality to this. But back button is clearly not mapped.

xodi · (This post was last modified: 2018-03-07, 07:06 by xodi.)

(2018-03-06, 22:51)garbear Wrote:
(2018-03-06, 18:19)xodi Wrote: The latest 2018-03-04 arm64 build crashed many times in my Android device, the previous build never crashed, I got the logcat for the crash:

Code:
F/libc (15607): invalid address or address of corrupt block 0x55a3e4c770 passed to dlfreeF/libc (15607): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xdeadbaad in tid 23639 (Thread-204927)I/DEBUG ( 171): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***I/DEBUG ( 171): Build fingerprint: 'Amazon/full_sloane/sloane:5.1.1/LVY48F/36.5.8.7_user_587700720:user/release-keys'I/DEBUG ( 171): Revision: '0'I/DEBUG ( 171): ABI: 'arm64'I/DEBUG ( 171): pid: 15607, tid: 23639, oom: 0, name: Thread-204927 >>> org.xbmc.kodi <<<I/DEBUG ( 171): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaadI/DEBUG ( 171): Abort message: 'invalid address or address of corrupt block 0x55a3e4c770 passed to dlfree'I/DEBUG ( 171): x0 3408b251dc991e56 x1 0000007fa16ab650 x2 0000000000000000 x3 0000000000000000I/DEBUG ( 171): x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010I/DEBUG ( 171): x8 7f7f7f7f7f7f7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 3408b251dc991e56I/DEBUG ( 171): x12 0000000000000001 x13 3408b251dc991e56 x14 0000000000000043 x15 0000000000000049I/DEBUG ( 171): x16 0000007fa1467ad0 x17 0000007fa13e9928 x18 0000000000000000 x19 00000055a3e4c770I/DEBUG ( 171): x20 0000007fa146e000 x21 00000055a3e4c780 x22 0000007fa146ee40 x23 0000007f7adfbee0I/DEBUG ( 171): x24 0000007f7adfcba0 x25 0000007f87dcf825 x26 0000007f7adfcba0 x27 0000007f848ceba0I/DEBUG ( 171): x28 0000007f848ceba0 x29 0000007f7adfbda0 x30 0000007fa140d9a4I/DEBUG ( 171): sp 0000007f7adfbda0 pc 0000007fa140d9ac pstate 0000000060000000I/DEBUG ( 171):I/DEBUG ( 171): backtrace:I/DEBUG ( 171): #00 pc 00000000000429ac /system/lib64/libc.so (dlfree+408)I/DEBUG ( 171): #01 pc 0000000000017af8 /system/lib64/libc.so (free+20)I/DEBUG ( 171): #02 pc 0000000000dbcb58 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE10deallocateEv+112)I/DEBUG ( 171): #03 pc 0000000000dbca8c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZNSt6__ndk16vectorINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS4_IS6_EEE13__move_assignERS8_NS_17integral_constantIbLb1EEE+24)I/DEBUG ( 171): #04 pc 0000000000db9354 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN13CVideoInfoTagaSEOS_+284)I/DEBUG ( 171): #05 pc 0000000001042764 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase14GetEpisodeInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagii+268)I/DEBUG ( 171): #06 pc 0000000001046e5c /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN14CVideoDatabase13LoadVideoInfoERKNSt6__ndk112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEER13CVideoInfoTagi+64)I/DEBUG ( 171): #07 pc 0000000001517454 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager15SetCurrentMovieER9CFileItem+380)I/DEBUG ( 171): #08 pc 0000000001516dc4 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN15CGUIInfoManager17SetCurrentItemJobENSt6__ndk110shared_ptrI9CFileItemEE+88)I/DEBUG ( 171): #09 pc 0000000001519920 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN18CSetCurrentItemJob6DoWorkEv+72)I/DEBUG ( 171): #10 pc 0000000001135cc4 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN10CJobWorker7ProcessEv+164)I/DEBUG ( 171): #11 pc 0000000001221530 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread6ActionEv+60)I/DEBUG ( 171): #12 pc 00000000012209f0 /data/app/org.xbmc.kodi-2/lib/arm64/libkodi.so (_ZN7CThread12staticThreadEPv+224)I/DEBUG ( 171): #13 pc 000000000001d68c /system/lib64/libc.so (_ZL15__pthread_startPv+52)I/DEBUG ( 171): #14 pc 00000000000198c4 /system/lib64/libc.so (__start_thread+16)

The error is:

invalid address or address of corrupt block 0x55a3e4c770 passed to dlfree

This indicates a DLL is being unloaded. Could this be causing the crash? Can you offer more context as to when Kodi crashes?

The stack trace indicates a crash in the function:

CVideoDatabase::LoadVideoInfo()CVideoDatabase::GetEpisodeInfo()

I was the last person to touch VideoDatabase.cpp with PR:13443, so maybe they're related.

Can you do some more testing and try to figure out how to reliably reproduce the crashes?[/font]

From the stack

Code:
CVideoInfoTag::operator=

CVideoDatabase::GetEpisodeInfo

CVideoDatabase::LoadVideoInfo

CGUIInfoManager::SetCurrentMovie

CGUIInfoManager::SetCurrentItemJob

Seems the same issue of https://github.com/xbmc/xbmc/pull/13373

Milhouse · 2018-03-07, 08:43

(2018-03-07, 07:05)xodi Wrote: Seems the same issue of https://github.com/xbmc/xbmc/pull/13373

See https://github.com/xbmc/xbmc/pull/13533#...-370927364 as this crash has been reported in LibreELEC RPi and x86_64 since build #0301, so at least this confirms it's not just a LibreELEC issue. Reverting PR13533 appears to resolve the issue.

**DaveBlake** · 2018-03-07, 10:18

(2018-03-07, 07:05)xodi Wrote: Seems the same issue of https://github.com/xbmc/xbmc/pull/13373

Yes it most probably is. Processing of GUI_MSG_UPDATE_ITEM message in CApplication (rather than CGUIInfoManager) the item is going out of scope on ocassions.

xodi · (This post was last modified: 2018-03-07, 20:29 by xodi.)

(2018-03-07, 10:18)DaveBlake Wrote:
(2018-03-07, 07:05)xodi Wrote: Seems the same issue of https://github.com/xbmc/xbmc/pull/13373
Yes it most probably is. Processing of GUI_MSG_UPDATE_ITEM message in CApplication (rather than CGUIInfoManager) the item is going out of scope on ocassions.

When this can be fixed? It's kind of nasty currently, when the playback (no matter local media or online video from YouTube addon) is stopped or ended, Kodi has a high chance (more than 50%) to crash on my device.