qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()

[Ian Nicholson]

Happened after I created a new project in the UbuntuSDK.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-dev-tools 5.4.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 23 14:43:26 2015
ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump
InstallationDate: Installed on 2014-12-11 (102 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -relocatable com.canonical.Oxide 1.3 /usr/lib/x86_64-linux-gnu/qt5/qml
ProcEnviron:
 LANGUAGE=en_US
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 SHELL=/bin/bash
Signal: 6
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 oxide::qt::WebViewAdapter::context() const () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 OxideQQuickWebView::~OxideQQuickWebView() () from /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0
 QQmlPrivate::QQmlElement<OxideQQuickWebView>::~QQmlElement() () from /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide/libqmloxideplugin.so
Title: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip kismet libvirtd lpadmin plugdev sambashare sudo wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1419616, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.