browser crashes saving image

Bug #1628635 reported by Bill Filler
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-download-manager (Ubuntu)
Fix Released
High
Michael Sheldon
webbrowser-app (Ubuntu)
Invalid
High
Olivier Tilloy

Bug Description

testing on unity8 desktop on xenial + overlay + silo 2010

Right click on image and press "Save Image"
will sometimes work, but crashes quite frequently 1/4 times roughly

Here is thread trace, full core attached

sing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.deskt'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f35552730a1 in QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&)
    () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
[Current thread is 1 (Thread 0x7f356042e780 (LWP 10477))]
(gdb) bt
#0 0x00007f35552730a1 in QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList<QVariant> const&)
    () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#1 0x00007f3553cc0858 in ?? () from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#2 0x00007f34bdfdf997 in Ubuntu::DownloadManager::SingleDownload::setAllowMobileDownload(bool) ()
   from /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
#3 0x00007f34bdfe18fc in Ubuntu::DownloadManager::SingleDownload::bindDownload(Ubuntu::DownloadManager::Download*)
    () from /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
#4 0x00007f355e955c24 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f3553ceacaf in Ubuntu::DownloadManager::Manager::downloadCreated(Ubuntu::DownloadManager::Download*) ()
   from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#6 0x00007f3553ce6770 in ?? () from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
#7 0x00007f355e955c24 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f35552adb9f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9 0x00007f35552adc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007f355e956719 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f355feb1b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f355feb7056 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f355e9292a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f355e92b16a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f355e97df53 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f355d60f1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f355d60f400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f355d60f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f355e97e35f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f355e926ffa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f355e92f6bc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x000000000042bf55 in main ()
(gdb)

Related branches

Bill Filler (bfiller)
Changed in webbrowser-app (Ubuntu):
assignee: nobody → Olivier Tilloy (osomon)
importance: Undecided → High
Revision history for this message
Olivier Tilloy (osomon) wrote :

It seems the crash is in libubuntu-download-manager-client1.
I’m attaching a complete backtrace, with the corresponding debug symbols installed.
Here is the relevant portion of the backtrace:

#4 0x00007f4b827d4858 in DownloadInterface::allowGSMDownload (allowed=true, this=0x0)
    at /build/ubuntu-download-manager-kJaokd/ubuntu-download-manager-1.3+16.04.20160909.1/src/downloads/client/ubuntu/download_manager/download_interface.h:60
#5 Ubuntu::DownloadManager::DownloadImpl::allowMobileDownload (this=0x1bb4960, allowed=<optimized out>)
    at /build/ubuntu-download-manager-kJaokd/ubuntu-download-manager-1.3+16.04.20160909.1/src/downloads/client/ubuntu/download_manager/download_impl.cpp:244
#6 0x00007f4af87dc997 in Ubuntu::DownloadManager::SingleDownload::setAllowMobileDownload(bool) ()
   from /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so

Bill Filler (bfiller)
Changed in ubuntu-download-manager (Ubuntu):
assignee: nobody → Michael Sheldon (michael-sheldon)
importance: Undecided → High
Revision history for this message
Olivier Tilloy (osomon) wrote :

I have rebuilt locally ubuntu-download-manager with added debug statements to try and understand why _dbusInterface is null when calling allowGSMDownload(bool) on it. With that version installed, I’m not getting the crash anymore.
I wonder if it could be some sort of silent ABI break due to a recent qt5 upload which fixes itself with a package rebuild?

Olivier Tilloy (osomon)
Changed in ubuntu-download-manager (Ubuntu):
status: New → In Progress
Changed in webbrowser-app (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-download-manager - 1.3+17.04.20161115-0ubuntu1

---------------
ubuntu-download-manager (1.3+17.04.20161115-0ubuntu1) zesty; urgency=medium

  * Reorder dbus object and service registration to be compatible with
    Qt 5.6 (LP: #1628635)

 -- Michael Sheldon <email address hidden> Tue, 15 Nov 2016 12:10:25 +0000

Changed in ubuntu-download-manager (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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