qmlplugindump crashed with SIGSEGV

Bug #1348300 reported by fcole90
This bug report is a duplicate of:  Bug #1332996: QtCreator often halts for a minute. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oxide-qt (Ubuntu)
New
Medium
Unassigned

Bug Description

Launching Ubuntu SDK starts qmlplugindump but it crashes.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: qtdeclarative5-dev-tools 5.2.1-3ubuntu15.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Jul 24 19:47:53 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump
InstallationDate: Installed on 2013-11-13 (253 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -relocatable com.canonical.Oxide 1.0 /usr/lib/x86_64-linux-gnu/qt5/qml
SegvAnalysis:
 Segfault happened at: 0x7f39e46760ba: mov (%rax),%rax
 PC (0x7f39e46760ba) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
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
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
Title: qmlplugindump crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-04-08 (107 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
fcole90 (fcole90) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 oxide::qt::ContentClient::GetNativeDisplay (this=0x1114ed0) at ../../../../qt/core/common/oxide_qt_content_client.cc:39
 oxide::(anonymous namespace)::BrowserMainParts::PreCreateThreads (this=0x12fbfb0) at ../../../../shared/browser/oxide_content_browser_client.cc:159
 content::BrowserMainLoop::PreCreateThreads (this=0x12fb5e0) at ../../../../third_party/chromium/src/content/browser/browser_main_loop.cc:522
 Run (this=0x1309530) at ../../../../third_party/chromium/src/base/callback.h:401
 content::StartupTaskRunner::RunAllTasksNow (this=0x13094c0) at ../../../../third_party/chromium/src/content/browser/startup_task_runner.cc:45

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in qtdeclarative-opensource-src (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Changing package to oxide-qt where the crash happens.

affects: qtdeclarative-opensource-src (Ubuntu) → oxide-qt (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.