| Summary: | Dolphin lags and then crashes when browsing locked device over KDE Connect | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Alex <alex765> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | akselmo, elvis.angelaccio, kfm-devel, me, postix, tarmoration |
| Priority: | NOR | Keywords: | wayland |
| Version: | 20.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Alex
2021-02-19 04:26:44 UTC
I'm now getting a crash when trying to browse my device, although this is when the device is unlocked. The lag before crashing is similar though. Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f1e3775e980 (LWP 112477))] [KCrash Handler] #6 0x00007f1e3e5e7292 in raise () from /lib64/libc.so.6 #7 0x00007f1e3e5d08a4 in abort () from /lib64/libc.so.6 #8 0x00007f1e3c4d142d in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=this@entry=0x7fff84916950, msg=msg@entry=0x7f1e3a079cb8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #10 0x00007f1e39feeef3 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/src/debug/qt5-qtwayland-5.15.2-4.fc34.x86_64/src/client/qwaylanddisplay.cpp:209 #11 QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/src/debug/qt5-qtwayland-5.15.2-4.fc34.x86_64/src/client/qwaylanddisplay.cpp:204 #12 0x00007f1e39ffd6fa in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x557557200820) at /usr/src/debug/qt5-qtwayland-5.15.2-4.fc34.x86_64/src/client/qwaylanddisplay.cpp:222 #13 0x00007f1e3c6cf4fd in doActivate<false> (sender=0x55755721ad40, signal_index=3, argv=0x7fff84916a50) at kernel/qobject.cpp:3898 #14 0x00007f1e3c6c99e7 in QMetaObject::activate (sender=sender@entry=0x55755721ad40, m=m@entry=0x7f1e3c963ac0 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #15 0x00007f1e3c69ba64 in QAbstractEventDispatcher::aboutToBlock (this=this@entry=0x55755721ad40) at .moc/moc_qabstracteventdispatcher.cpp:143 #16 0x00007f1e3c6eb6d2 in QEventDispatcherGlib::processEvents (this=0x55755721ad40, flags=...) at kernel/qeventdispatcher_glib.cpp:410 #17 0x00007f1e3c69d9b2 in QEventLoop::exec (this=this@entry=0x7fff84916b70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #18 0x00007f1e3c6a5544 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #19 0x00007f1e3e7cfd3d in kdemain () from /lib64/libkdeinit5_dolphin.so #20 0x00007f1e3e5d1b75 in __libc_start_main () from /lib64/libc.so.6 #21 0x0000557555d380ae in _start () [Inferior 1 (process 112477) detached] I have the same issue, in my experience it's not specific to Dolphin/KDE Connect but happens any time a KDE application (or any Qt application?) under Wayland hangs and you keep interacting with it while it's hanging (if you do nothing and wait until it's responsive again, it will not crash). It is usually noticable with network shares though, including the KDE Connect one. "The Wayland connection broke. Did the Wayland compositor die?" I think that Wayland closes the connection to any application that doesn't receive input events after some buffer for them filled up, but that's just a guess from how it behaves. This is probably https://bugreports.qt.io/browse/QTBUG-66997. Looks like I was right: > I looked a bit into this... It's happening because you block the GUI thread > for a long time (which you shouldn't do), no events will be read and the > Wayland socket buffer will eventually fill up if you generate a lot of > input in a very short time (the compositor should ideally stop sending > events when the client doesn't answer ping events). When the socket buffer > fills up, the client will be disconnected (closed). Also see bug #392376. Created attachment 142014 [details]
New crash information added by DrKonqi
dolphin (20.04.2) using Qt 5.12.7
- What I was doing when the application crashed:
Looking at the internal storage directory of my kde-connected phone and hovering my mouse over the internal secondary drive of my computer at the devices section on the left.
- Custom settings of the application:
KDEConnect was in use and my phone's whole internal storage was exposed and on. Dolphin was probably counting the items in each of the directory as I was in details view mode. I have some populated directories in my phone's internal storage and dolphin had the time to count all of them, at least at a single level depth.
-- Backtrace (Reduced):
#6 0x00007f31d623487b in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1907
#7 QMessageLogger::fatal (this=this@entry=0x7ffc6128a820, msg=msg@entry=0x7f31c71f1be0 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:888
#8 0x00007f31c718b4ed in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:179
#9 0x00007f31c718b53e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55e5c56519e0) at qwaylanddisplay.cpp:192
[...]
#12 0x00007f31d646f7f8 in QSocketNotifier::activated (this=this@entry=0x55e5c56b8bd0, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:140
*** This bug has been marked as a duplicate of bug 462390 *** |