Details
-
Bug
-
Resolution: Duplicate
-
P1: Critical
-
None
-
5.7.1
-
None
Description
The attached QtQML sample application crashes with mysterious backtrace when loading/executing JavaScript file from a .qml file:
1 __GI_raise raise.c 54 0x7ffff6056428 2 __GI_abort abort.c 89 0x7ffff605802a 3 qt_message_fatal qlogging.cpp 1710 0x7ffff6a1cdc2 4 QMessageLogger::fatal qlogging.cpp 816 0x7ffff6a1daca 5 qt_assert qglobal.cpp 3091 0x7ffff6a16bce 6 QQmlTypeLoader::getType qqmltypeloader.cpp 1628 0x7ffff71f374c 7 QQmlComponentPrivate::loadUrl qqmlcomponent.cpp 660 0x7ffff71d20cf 8 QQmlComponent::QQmlComponent qqmlcomponent.cpp 524 0x7ffff71d2192 9 QQmlComponent::QQmlComponent qqmlcomponent.cpp 505 0x7ffff71d21a9 10 QQuickViewPrivate::execute qquickview.cpp 105 0x7ffff7be81ac 11 QQuickView::setSource qquickview.cpp 236 0x7ffff7be825b 12 main Main.cc 8 0x400e18
The JavaScript that crashes the QML engine was generated from Ruby sources by a ruby-to-js compiler called Opal. The crash occurs in multiple code locations (commenting the crash out in one place causes the crash to occur somewhere else). The .js file uses no custom native extensions or plugins.
Tested on Ubuntu 17.04 x86_64, Qt 5.7.1
Attachments
Issue Links
- duplicates
-
QTBUG-58837 QQmlComponent can no longer load local, relative URLs
- Closed