qt/qtdeclarative.git, branch 5.10

Merge remote-tracking branch 'origin/5.9' into 5.10

2018-02-07T10:03:01+00:00

Change-Id: I3b250545e334f50dcef1a75acdef51820d34079a

Fix memory leak with deferred properties

2018-02-06T20:59:44+00:00

This is a regression introduced with commit
3b6eeee177b64eebe240d51be0c7bb5f031471d8 in the 5.9 branch. When
constructing an object with deferred properties and not running
qmlExecuteDeferred, then the deferred data would never get deleted
because the bindings list remains non-empty and we would leak the
deferred data as well as the entire compilation unit behind it.

This happens for example when declaring when instantiating a QML file
with states:

   states: [ State { ... }, State { ... }, ... }

Unless every state is entered, its deferred changes property is never
applied (via qmlExecuteDeferred) and thus the defer data is leaked.

Task-number: QTBUG-66189
Change-Id: I1b2119c601d1e0ab4e37f53d4cf2f569586ee883
Reviewed-by: J-P Nurmi 
Reviewed-by: Lars Knoll

Clean up manual refcounting of compilation units

2018-02-06T20:59:40+00:00

Replace manual use in QQmlData and QQmlData::DeferredData with
QQmlRefPointer.

Due to forward declaration trouble this required declaring a non-inline
constructor/destructor for QQmlData and DeferedData and disabling
copying, so that not every C++ compilation unit including qqmldata_p.h
needs to instantiate the QQmlRefPointer destructor and thus know whether
QV4::CompiledData::CompilationUnit has release(), etc. The out-of-line
declarations however should not have any negative impact as the only
call sites are within qqmlengine.cpp, too.

Change-Id: I2e8295cb0d7f876a5d7d18765dbac285184e6c99
Reviewed-by: Lars Knoll

Add back the optional heaptrack trace points

2018-02-06T10:58:46+00:00

This approach tracks object allocations only,
when slots from already allocated memory segment are used.


Change-Id: I514b974d7580c1236264bec96dc1abe594585e86
Reviewed-by: Milian Wolff 
Reviewed-by: Ulf Hermann 
Reviewed-by: Simon Hausmann

Use the GL context shared in the render context

2018-02-06T09:19:54+00:00

.. instead of calling QOpenGLContext::currentContext(), which in turn
accesses the thread-local storage.

Change-Id: I773686deb2a745e066b0878a6ccb087afb81774d
Reviewed-by: Simon Hausmann 
Reviewed-by: Tuukka Turunen

touchEvent_propagation: remove some QWaits

2018-02-05T15:02:29+00:00

I doubt it will make the test any less flaky, but may be an improvement.

Task-number: QTBUG-53916
Change-Id: I3901ab26107abfd1420947392232243ad8c40ead
Reviewed-by: Mitch Curtis

Document that Q_GADGET classes cannot be used with newQMetaObject()

2018-02-05T12:17:01+00:00

Task-number: QTBUG-62007
Change-Id: I63d5a57163b36bc8629930e1cda8d5afa1e77d15
Reviewed-by: Simon Hausmann

Merge remote-tracking branch 'origin/5.9' into 5.10

2018-02-05T09:25:15+00:00

 Conflicts:
	tests/auto/quickwidgets/qquickwidget/tst_qquickwidget.cpp

Change-Id: I64f7c1d776fab3cad4530f291b93afd2a8fb8533

QML: Collapse all NaNs into one single (encoded) NaN

2018-02-05T09:15:25+00:00

The idea of NaN boxing is to use one single NaN as a "true" NaN, and all
others as a boxed value. So when encoding some NaN, be sure to use that
one "true" NaN. Otherwise, it will be interpreted as an encoded value.

Task-number: QTBUG-65998
Change-Id: Ia6e4641be180f3d626c40a57b473f181358e04db
Reviewed-by: Simon Hausmann

Add QQuickWindow synthMouseFromTouch test

2018-02-03T12:49:07+00:00

Similar to the one for QQuickWidget, it tests the effect of
AA_SynthesizeMouseForUnhandledTouchEvents and verifies the
source() of the synthesized mouse event.

Change-Id: Ib706b5cc7b9a374850f3197ca6ce2c3aed4d1ba2
Reviewed-by: Jan Arve Sæther