[dolphin] [Bug 433218] Dolphin lags and then crashes when browsing locked device over KDE Connect

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=433218

--- Comment #4 from tarmoration at gmail.com ---
Created attachment 142014
  --> https://bugs.kde.org/attachment.cgi?id=142014&action=edit
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 at entry=0x7ffc6128a820,
msg=msg at 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 at entry=0x55e5c56b8bd0, _t1=<optimized out>, _t2=...) at
.moc/moc_qsocketnotifier.cpp:140

-- 
You are receiving this mail because:
You are on the CC list for the bug.