blabble + qt5.3 on flo #73 crash

Bug #1327667 reported by Alan Pope 🍺🐧🐱 🦄
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qtchooser (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Install blabble.
Add the qt5.3 ppa https://launchpad.net/~ci-train-ppa-service/+archive/landing-005
Reboot
Start blabble
Observe crash

libust[25934/25937]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:886)
libust[25934/25937]: Error: Error opening shm /lttng-ust-wait-5-32011 (in get_wait_shm() at lttng-ust-comm.c:886)
callbacks 0xb3ca040d 0xb3ca0305

Is all I get from the app crash.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: qtchooser 39-g4717841-3
Uname: Linux 3.4.0-3-flo armv7l
ApportVersion: 2.14.3-0ubuntu1
Architecture: armhf
Date: Sun Jun 8 00:32:55 2014
Dependencies:
 gcc-4.9-base 4.9.0-5ubuntu2
 libc6 2.19-0ubuntu6
 libgcc1 1:4.9.0-5ubuntu2
 libstdc++6 4.9.0-5ubuntu2
 multiarch-support 2.19-0ubuntu6
InstallationDate: Installed on 2014-06-07 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140607)
SourcePackage: qtchooser
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
tags: added: qt5.3
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qtchooser (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Still crashes, also with the 5.3.1 qtdeclarative snapshot.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

In the automated testing, blabble is seen crashing also on 5.2. If it's similarly on start of the app, this is not Qt 5.3 specific.

Changed in qtchooser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

Tested manually on a qt5.2 device and blabble works fine. Tested again manually on 5.3 and it crashes reliably.

Changed in qtchooser (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I see this too on image 100 in the emulator. Blabble will start if you remove the u1db ~/.local/share/com.ubuntu.developer.jdstrand.blabble/blabble.u1db. If you close the app and then try to restart it, it crashes until you remove ~/.local/share/com.ubuntu.developer.jdstrand.blabble/blabble.u1db again. This suggest a place to start would be U1db. components/Storage.qml uses 'import U1db 1.0 as U1db'.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Actually, that may be a red herring. If I don't delete blabble.u1db, but keep trying to launch it, eventually it will launch without crashing. I also have no problems with this app on the latest promoted image which still has 5.2.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

If it helps, blabble uses a QML SplashScreen and Loader element to show a static image while loading ui/MainView.qml. I wonder if something changed in 5.3 wrt this.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

"In the automated testing, blabble is seen crashing also on 5.2." What automated testing? Blabble is not part of any automated testing that I am aware of.

Revision history for this message
Olivier Tilloy (osomon) wrote :

I can reliably reproduce the crash on flo with image #101. Here is the backtrace I’m getting:

#0 operator-> (this=0x2c)
    at ../../include/QtQml/5.3.0/QtQml/private/../../../../../src/qml/qml/ftw/qflagpointer_p.h:221
#1 allCreatedObjects (this=0x0)
    at ../../include/QtQml/5.3.0/QtQml/private/../../../../../src/qml/qml/qqmlobjectcreator_p.h:92
#2 QQmlVMEGuard::guard (this=this@entry=0x1476ff4, creator=0x0)
    at qml/qqmlvme.cpp:116
#3 0xb6c2e3f8 in QQmlIncubatorPrivate::incubate (this=0x1476fa8, i=...)
    at qml/qqmlincubator.cpp:389
#4 0xb6c2eaf6 in QQmlIncubationController::incubateFor (
    this=this@entry=0x1303b70, msecs=<optimized out>)
    at qml/qqmlincubator.cpp:404
#5 0xb6e1a544 in incubate (this=0x1303b68) at items/qquickwindow.cpp:135
#6 QQuickWindowIncubationController::timerEvent (this=0x1303b68)
    at items/qquickwindow.cpp:118
#7 0xb627ceca in QObject::event(QEvent*) ()
   from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#8 0xb67b79a4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#9 0xb67bb13a in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
Cannot access memory at address 0x2d4ff0e0

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

This seems related to the splashscreen/deferred loading functionality I implemented. I have uploaded 0.4.1 to the store which reverts this, but attached is 0.4 which still has it to help reproduce this bug.

Changed in qtchooser (Ubuntu):
importance: Undecided → High
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.