Details
-
Bug
-
Resolution: Incomplete
-
P1: Critical
-
None
-
4.8.1, 4.8.4
-
None
-
Mint Linux, Ubuntu Linux, 4.8.1, 4.8.4
Description
There appears to be a bug in the QML engine where QEvent::DeferredDelete is being sent to the root object of the QML application app at startup. A few things that have worked around the issue include:
1. Commenting out different portions of the QML application code
2. Setting QML_DISABLE_OPTIMIZER to true
3. Calling QDeclarativeView::setSource twice with the same QML file
There are no destroy calls in the application and I have tried the JS gc workaround discussed here: http://qt-project.org/forums/viewthread/25485.
Backtrace is attached.