Merge lp:~aacid/unity8/no_model_reset_from_destructor into lp:unity8
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Michael Zanetti | ||||
Approved revision: | 997 | ||||
Merged at revision: | 1007 | ||||
Proposed branch: | lp:~aacid/unity8/no_model_reset_from_destructor | ||||
Merge into: | lp:unity8 | ||||
Diff against target: |
12 lines (+1/-1) 1 file modified
tests/mocks/Unity/Indicators/fakeindicatorsmodel.cpp (+1/-1) |
||||
To merge this branch: | bzr merge lp:~aacid/unity8/no_model_reset_from_destructor | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Needs Fixing | |
Michael Zanetti (community) | Approve | ||
Review via email: mp+225127@code.launchpad.net |
Commit message
Fix valgrind warning by not emitting reset on model destructor
That won't be supported until Qt 5.4
More info at https:/
Warning was
==16693== Invalid read of size 8
==16693== at 0x72B19A0: QQmlContext:
==16693== by 0x736C82B: QQmlDelegateMod
==16693== by 0x7372AE6: QQmlDelegateMod
==16693== by 0x7397224: QQmlDelegateMod
==16693== by 0x739769E: QQmlDelegateMod
==16693== by 0x66379CC: QMetaObject:
==16693== by 0x65AEEFD: QAbstractItemMo
==16693== by 0x23461EFD: FakeIndicatorsM
==16693== by 0x23461E13: FakeIndicatorsM
==16693== by 0x2345C073: QQmlPrivate:
==16693== by 0x2345C0A3: QQmlPrivate:
==16693== by 0x663636B: QObjectPrivate:
==16693== Address 0x1862d448 is 8 bytes inside a block of size 16 free'd
==16693== at 0x4C2C2BC: operator delete(void*) (vg_replace_
==16693== by 0x72B21B8: QQmlContextData
==16693== by 0x7293458: QQmlPrivate:
==16693== by 0x6C0CADD: QQmlPrivate:
==16693== by 0x663636B: QObjectPrivate:
==16693== by 0x663F0EB: QObject::~QObject() (in /usr/lib/
==16693== by 0x6BF64B5: QQuickItem:
==16693== by 0x6C0CAE5: QQmlPrivate:
==16693== by 0x663636B: QObjectPrivate:
==16693== by 0x663F0EB: QObject::~QObject() (in /usr/lib/
==16693== by 0x6BF64B5: QQuickItem:
==16693== by 0x6C0CAE5: QQmlPrivate:
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?
No, but it's only test code and the valgrind warning is gone
* 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
* Did you perform an exploratory manual test run of the code change and any related functionality?
yes
* Did CI run pass? If not, please explain why.
waiting...