https://bugs.kde.org/show_bug.cgi?id=351839
--- Comment #18 from Thomas Lübking <thomas.luebk...@gmail.com> --- No idea whether it's "fixed", but QML apparently gets a completely new data allocation mechanism: http://code.qt.io/cgit/qt/qtdeclarative.git/commit/src/qml/jsruntime/qv4stringobject.cpp?id=17a0c271e0ec606d15fc87dab23b2e3750c0e301 So we won't see *this* backtrace for sure on Qt 5.6 The problem is however the nullptr deref of the "string" member and that "merely" changed from "string = ic->engine->newString();" to "string = internalClass->engine->id_empty()->d();" - neither looks like there should ever be a nullptr. Maybe even the StringObject is nullptr. -- You are receiving this mail because: You are watching all bug changes.
