qmlscene crashed with SIGSEGV in g_type_check_instance()

Bug #1214929 reported by Rick Spencer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qtdeclarative-opensource-src (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Was running an app from QtCreator when I got this crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: qmlscene 5.0.2-6ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 21 10:12:02 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene
InstallationDate: Installed on 2013-04-23 (119 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene -I /home/username/Projects/app-lifecycle -I /usr/bin -I /usr/lib/x86_64-linux-gnu/qt5/qml /home/username/Projects/app-lifecycle/ApplicationLifecycleApp.qml
SegvAnalysis:
 Segfault happened at: 0x7f07e7bf6759 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f07e7bf6759) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
 g_type_check_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: qmlscene crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to saucy on 2013-08-14 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x28962b0) at /build/buildd/glib2.0-2.37.5/./gobject/gtype.c:4082
 g_signal_emit_valist (instance=0x28962b0, signal_id=381, detail=0, var_args=var_args@entry=0x7fff95745c58) at /build/buildd/glib2.0-2.37.5/./gobject/gsignal.c:3105
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.37.5/./gobject/gsignal.c:3382
 position_provider_changed (proxy=<optimized out>, name=<optimized out>, description=<optimized out>, service=<optimized out>, path=<optimized out>, client=<optimized out>) at geoclue-master-client.c:172
 marshal_dbus_message_to_g_marshaller (closure=0x2bc6c10, return_value=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=0x7fff95745f10, marshal_data=0x0) at dbus-gproxy.c:1736

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 :

Marking the bug as Incomplete to indicate it's probably not reproducible anymore. Qt Declarative script engine was rewritten in the Qt 5.2.1 and it's likely the crashes that happened with Qt 5.0.2 do not happen or are different with the new Qt.

Changed in qtdeclarative-opensource-src (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qtdeclarative-opensource-src (Ubuntu) because there has been no activity for 60 days.]

Changed in qtdeclarative-opensource-src (Ubuntu):
status: Incomplete → Expired
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.