2018-08-02, 01:58
In PR 13972 the design/implementation for loading profiles was changed. When logging off a profile the masterprofile is loaded, just for the purpose of loading the loginscreen.
LoadProfile() in ProfileManager.cpp does some things, then calls FinalizeLoadProfile(). There is a bool m_profileLoadedForLogin but it doesn't seem like we use this. In particular, when FinalizeLoadProfile() gets called. I don't see a reason to do many of these things when we load the masterprofile just to allow us to load the "real" profile. It just slows things down, We also load the masterprofile skin's startup window which fires off any number of <onload> events for no reason. One user has requested support, as his masterprofile is causing a PVR EPG update which blocks him for 10 secs before he can access the loginscreen and load the profile he actually wants.
scott s.
.
LoadProfile() in ProfileManager.cpp does some things, then calls FinalizeLoadProfile(). There is a bool m_profileLoadedForLogin but it doesn't seem like we use this. In particular, when FinalizeLoadProfile() gets called. I don't see a reason to do many of these things when we load the masterprofile just to allow us to load the "real" profile. It just slows things down, We also load the masterprofile skin's startup window which fires off any number of <onload> events for no reason. One user has requested support, as his masterprofile is causing a PVR EPG update which blocks him for 10 secs before he can access the loginscreen and load the profile he actually wants.
scott s.
.
