Merge lp:~aacid/unity8/workaround_qt47709 into lp:unity8
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Gerry Boland | ||||
Approved revision: | 1903 | ||||
Merged at revision: | 1908 | ||||
Proposed branch: | lp:~aacid/unity8/workaround_qt47709 | ||||
Merge into: | lp:unity8 | ||||
Diff against target: |
26 lines (+5/-0) 2 files modified
qml/Components/UnityInputInfo/UnityInputInfo.qml (+2/-0) qml/OrientedShell.qml (+3/-0) |
||||
To merge this branch: | bzr merge lp:~aacid/unity8/workaround_qt47709 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gerry Boland (community) | Approve | ||
Review via email: mp+267647@code.launchpad.net |
Commit message
Workaround for bug 1473471
After three days of debugging I've been able to figure out why it is crashing, why it's random and i can provide a quick workaround in unity8 code.
## Why is it crashing? ##
The problem exists because we use the QML cache and because Qt has this bug https:/
The bug in Qt means that if for types with extended properties (Image and "source" in our case coming from the SDK) an Item is created before the type is extended, all subsquent items of the same type won't see the extended property either.
Since we're using the QML cache this means that the code loaded from the cache expects the extended property to be there, so when it access such property, it will crash.
## Why is it random? ##
It's random because the QML file loading is not always done in the *exact* same order, and thus in some cases the first Image is created in a file that imports Ubuntu.Components and in some cases the first image is created in a file that does not.
## How to workaround it? ##
A quick workaround is making sure Ubuntu.Components is imported in the first file that is imported, in unity8's case UnityInputInfo.qml that is a singleton imported from the root file (OrientedShell.qml)
Description of the change
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
Explanation makes sense, happy to approve