| bshah |
| Plasma |
KCMInit is loaded early in startkde, and it blocks all other processes
from starting until it is complete.
This can be up to 1.1 seconds.
(http://imgh.us/bootchart-20160928-1316.svg)
A sizable amount of time (46% of CPU) is spent loading our QPT. This
isn't very useful given none of the kcm_init scripts have any UI and
it's not something they should have. It's only a QGuiApplication so that
they have an X connection.
Checked it ran without errors
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
| startkde/kcminit/main.cpp | ||
|---|---|---|
| 256 | This is a static and docs explicitly mention "This function must be called before creating the QGuiApplication object", http://doc.qt.io/qt-5/qguiapplication.html#setDesktopSettingsAware | |
Reopening due to @broulik's comment. This clearly must be called before creating the QGuiApplication as the ctor of QGuiApplication creates the QPT plugin.