Bug Kodi 18 x64 crashing when using profiles
#1
All builds after KodiSetup-20180201-f621a026-master-x64.exe are crashing on video playback if logged in using a profile.

I've installed fresh using the portable method.  I then copy in my sources.xml and mediasources.xml into the portable_data folder, open Kodi and add a new profile.  I choose to copy sources from default.  I then log off Master, and select my new profile.

When I enter the files section and select a movie, it WILL play at this time.  When I close Kodi, and re-open, select my new profile, and enter files section and play a movie, it crashes immediately.  Something has broken with profiles.  

I've pasted a dmp to: https://pastebin.com/Bepp5v9R

Never used that site before, so I'm not 100% it took the contents, so here is what I see in WinDbg:

Loading Dump File [U:\Kodi Crash Dumps\kodi_crashlog-18.0-ALPHA1 Git_20180308-f0dce70c48-20180309-143422.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Debug session time: Fri Mar  9 14:34:22.000 2018 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:00:26.000
................................................................
............................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(8d4.2218): Access violation - code c0000005 (first/second chance not available)
ntdll!NtGetContextThread+0x14:
00007ff8`475870b4 c3              ret
0:000> .ecxr
rax=00007f2f9be634f8 rbx=0000000000000000 rcx=0000000000000048
rdx=0000000000000000 rsi=00000069e9af71e8 rdi=0000000000000000
rip=00007ff834e688c6 rsp=00000069e9af7110 rbp=0000000000000048
 r8=000002685c2124c0  r9=0000000000008000 r10=000002686638e850
r11=00000069e9af7100 r12=00000069e9af7e90 r13=0000000000000000
r14=0000000000000000 r15=00000069e9af7e90
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
msvcp140!mtx_do_lock+0x22:
00007ff8`34e688c6 8b01            mov     eax,dword ptr [rcx] ds:00000000`00000048=HuhHuh??
Reply
#2
After some quick code review, it looks like this Jan 24th commit is what broke profiles:

https://github.com/xbmc/xbmc/commit/0f19...401588fb1e

There are a lot of removals of CProfilesManager::GetInstance()

Am I posting this in the correct forum?  I am new here...  No devs have responded.
Reply
#3
Probably the main support forum is best for bug reporting.  I have also seen what might be problems in profiles.  Creating a new profile with new settings / sources seems to work OK.  I'm not sure of all the variations possible with new profiles so not 100% on how best to test.

scott s.
.
Reply

Logout Mark Read Team Forum Stats Members Help
Kodi 18 x64 crashing when using profiles0