[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[MountainX]

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

--- Comment #31 from MountainX  ---
I look forward to testing git commit 60475571926d79ffad90061985f39c3ce9c686d1.
Thanks for the working being done on it. I believe that fix will help with the
issue of changes to the Places bookmarks being very slow.

In the OP and the comments of this bug report at least two other issues are
mentioned:

1. a memory leak
2. Dolphin and KDE file-open dialogs in all KDE applications open slowly. It
takes about 2 seconds for the file-open dialog to display in Kate or any other
application.

The memory leak may not be related to this issue (Dolphin slow for specific
operations) so I won't say more about it.

However, the Places bookmarks are related to the long delay in Dolphin and KDE
file-open dialogs opening up. I state this because when I delete
~/.local/share/user-places.xbel, the issue goes away and these dialogs (and
Dolphin) open very quickly.

That should be easy to confirm. If you make a large enough bookmarks list to
see the problem on adding or editing a bookmark, you should also see file-open
dialogs become slow to come up.

My question is should I make a separate bug report or is this likely related to
the fixes being done here?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[David Faure]

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

--- Comment #30 from David Faure  ---
Git commit 60475571926d79ffad90061985f39c3ce9c686d1 by David Faure, on behalf
of Méven Car.
Committed on 22/05/2020 at 17:53.
Pushed by dfaure into branch 'master'.

KUrlNavigatorPlacesSelector: only update once the menu on changes

Previously the updateMenu function was called twice for each place
added/removed.

M  +2-0src/filewidgets/kfileplacesmodel.cpp
M  +7-0src/filewidgets/kfileplacesmodel.h
M  +1-5src/filewidgets/kurlnavigatorplacesselector.cpp

https://invent.kde.org/frameworks/kio/commit/60475571926d79ffad90061985f39c3ce9c686d1

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[MountainX]

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

--- Comment #29 from MountainX  ---
>> Maybe it would also help to have an option to tell this code to ignore
>> certain mounts?
>Right click on the entry in the place menu > Hide, it's that simple.

That does not remove the items from ~/.local/share/user-places.xbel

Instead of "hide" I was suggesting an "ignore" feature that would avoid placing
unwanted system mount points in user-places.xbel. The name of the file implies
they are user-places, which seems to indicate it should contain only entries
the user is interested in. Just my thoughts.

Thank you for your work on this issue!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Méven Car]

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

--- Comment #28 from Méven Car  ---
(In reply to MountainX from comment #27)
> 
> I would like to add an observation. In my case I do not have to add "many
> many" entries.  Dolphin automatically adds entries for all mount points. The
> mere fact that my system has 15 NFS mounts and more than one local storage
> device is sufficient to cause this issue with a modest number of my own
> bookmark entries in Places.

Fixing this bug could fix the issue you are describing.
If not, it sounds like it is a different bug and we might want to open a new
bug with your specific case.
Wait to see once this bug is resolved fix your issue before opening a new one. 

> 
> If I delete these autogenerated entries from `user-places.xbel`, Dolphin
> puts them back -- even though I don't need or use them in Dolphin. 
> 
> Maybe it would also help to have an option to tell this code to ignore
> certain mounts?

Right click on the entry in the place menu > Hide, it's that simple.
It works on places groups too, and can be undone using the "show hidden places"
of the groups context menu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[MountainX]

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

--- Comment #27 from MountainX  ---
> I was able to reproduce the bug adding many many entries to my bookmark 
> menu...

That's good news. Thanks for your work on this issue.

I would like to add an observation. In my case I do not have to add "many many"
entries.  Dolphin automatically adds entries for all mount points. The mere
fact that my system has 15 NFS mounts and more than one local storage device is
sufficient to cause this issue with a modest number of my own bookmark entries
in Places.

If I delete these autogenerated entries from `user-places.xbel`, Dolphin puts
them back -- even though I don't need or use them in Dolphin. 

Maybe it would also help to have an option to tell this code to ignore certain
mounts?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Méven Car]

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

Méven Car  changed:

   What|Removed |Added

 CC||meve...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #26 from Méven Car  ---
I was able to reproduce the bug adding many many entries to my bookmark menu
and get a trace:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f01b57b2d39 in QObjectPrivate::setParent_helper(QObject*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x7f01b57b2d39 in QObjectPrivate::setParent_helper(QObject*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f01b57b3623 in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f01b6276257 in QAction::~QAction() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x7f01b627628d in QAction::~QAction() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x7f01b6403fdf in QMenu::clear() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7f01b76a88e3 in KDEPrivate::KUrlNavigatorPlacesSelector::updateMenu
(this=0x564235251f80)
at
/home/meven/kde/src/kio/src/filewidgets/kurlnavigatorplacesselector.cpp:72
#6  0x7f01b57ab458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f01b572ba29 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f01b76782b3 in KFilePlacesModel::Private::_k_reloadBookmarks (thi


#0  0x7f01b6a482a4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5
#1  0x7f01b6a48ae9 in QDomNode::namedItem(QString const&) const () from
/usr/lib/x86_64-linux-gnu/libQt5Xml.so.5
#2  0x7f01b75c09ae in cd (node=..., name=..., create=) at
/home/meven/kde/src/kbookmarks/src/kbookmark.cpp:48
#3  0x7f01b75c3276 in KBookmark::metaData (this=this@entry=0x7ffeb71ba1a0,
owner=..., create=create@entry=false)
at /home/meven/kde/src/kbookmarks/src/kbookmark.cpp:586
#4  0x7f01b75c47fd in KBookmark::metaDataItem
(this=this@entry=0x7ffeb71ba1a0, key=...)
at /home/meven/kde/src/kbookmarks/src/kbookmark.cpp:36
#5  0x7f01b766dec8 in KFilePlacesItem::isDevice
(this=this@entry=0x56423b41eea0)
at /home/meven/kde/src/kio/src/filewidgets/kfileplacesitem.cpp:101
#6  0x7f01b766f8b3 in KFilePlacesItem::data (this=0x56423b41eea0, role=0)
at /home/meven/kde/src/kio/src/filewidgets/kfileplacesitem.cpp:164
#7  0x7f01b767211b in KFilePlacesModel::data (this=0x564235563d10,
index=..., role=)
at /home/meven/kde/src/kio/src/filewidgets/kfileplacesmodel.cpp:538
#8  0x7f01b7671f8f in KFilePlacesModel::text (this=,
index=...)
at /home/meven/kde/src/kio/src/filewidgets/kfileplacesmodel.cpp:439
#9  0x7f01b76a8b55 in KDEPrivate::KUrlNavigatorPlacesSelector::updateMenu
(this=0x56423554d790)
at
/home/meven/kde/src/kio/src/filewidgets/kurlnavigatorplacesselector.cpp:91
#10 0x7f01b57ab458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f01b572ba29 in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

The culprit is `KUrlNavigatorPlacesSelector::updateMenu` clears the whole menu
for each place insertion or removal, twice over (because of dataChanged and
rowsInserted connection). And the inner loop of updateMenu is not light. Making
adding new places an exponentially slower operation.

To solve this issue :
1/ We need to call updateMenu once per update to the model
2/ We need to make the update progress incremental idealy

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[MountainX]

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

--- Comment #25 from MountainX  ---
close Dolphin
mv ~/.local/share/user-places.xbel ~/.local/share/user-places.xbel.bak
open Dolphin

The above steps eliminate the slowness. That also eliminates all my Places
bookmarks, so it is not a solution. For testing, it does indicate that the
comment by Nate Graham (2018-05-08) is looking in the right direction.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[MountainX]

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

MountainX  changed:

   What|Removed |Added

 CC||davestechs...@gmail.com

--- Comment #24 from MountainX  ---
I'm investigating slow UI responsiveness in Dolphin on my desktop & noticed
this bug report. I also run Arch Linux. What caught my attention is this part
of the report: "In particular, adding or moving a bookmark in the Places panel
has a delay of several seconds."

That is the same behavior I'm observing.

Adding a new bookmark to Dolphin's Places sidebar has a long delay and it
causes the Dolphin UI to freeze for this time. The same delay is seen if I edit
the item in Places and change its display name, or remove an item.

I timed dragging & dropping a local directory onto Places. It took 15 seconds
for that item to appear in Places, but Dolphin was still unresponsive for an
addition 10 seconds. It was about 25 seconds before I could navigate or use the
UI. The delay is almost the same for a name change. Deleting an item from
Places seems to require about 15 seconds.

Other operations in Dolphin do not appear to be slow, and the overall
experience is not slow. There is one thing I notice that it not mentioned by
the OP. All KDE file-open dialogs open slowly. It takes about 2 seconds for the
file-open dialog to display in Kate or any other application. GTK file-open
dialogs are nearly instant.

wc -l ~/.local/share/user-places.xbel
1649

I use KDE on a number of different devices. The computer used for the timings
mentioned above has 128 GB of RAM, a Samsung Pro NVMe, nVidia RTX 2080 GPU and
an Intel i9-9900K. It has 15 NFS shared folders mounted. It has a large & slow
internal HDD that is only used for automated backups and I don't open this
backup location in Dolphin anyway.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[QP]

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

QP  changed:

   What|Removed |Added

 CC||qipu...@gmail.com

--- Comment #23 from QP  ---
I have also been noticing huge slowdowns with Dolphin for a while now. First
noticed it around the time this bug was opened. 

My issues are the same as those already reported here. Previously, I was able
to keep Dolphin open. Now I have to close Dolphin after each use.


Software:
dolphin 19.04.3
plasmashell 5.16.4
Qt 5.13.0
kernel: 5.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Alexander Potashev]

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

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #22 from bugreporte...@gmail.com ---
The issue still exists.

Software versions:
dolphin 18.12.2
plasmashell 5.15.0
Qt version 5.12.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Kevin Gagnon]

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

Kevin Gagnon  changed:

   What|Removed |Added

 CC||cordonfree...@gmail.com

--- Comment #21 from Kevin Gagnon  ---
Running KDE Neon 18.04, since an update sometime in october, I've been noticing
huge slowdowns with Dolphin also, I was out of country for a while so I had a
big backlog of updates and can't nail down exactly when it started, am
currently up to date on all packages.

I average 6ish tabs open in dolphin, after some days, maybe only hours of
general usage, I can see the dolphin process spike to 100% cpu when I am
hovering over files, the animation of hovering over the files is also very
lagged like its really struggling, the cpu spiking will stop if i dont move the
mouse, and resume as I hover over another file, even simple small txt files.
The same behavior is seen when switching tabs as well.

I tried closing all tabs down to just 1 and it was noticeably better bug still
laggy, only after fully restarting dolphin did I get normal fast performance
again. I opened up a bunch of tabs (6) to various folders I work in and was
still fast since the restart.

I'm a programmer but not experienced in linux development, but this feels like
a resource build up occurring that isn't getting cleaned up, causing heavy cpu
work just to do basic things.

I'd be happy to try debugging or monitoring logs as the issue returns but at
the moment I wouldn't know where to start in that regard xD.

Software:
dolphin 18.08.3
plasma 5.14.4
frameworks 5.52.0
qt: 5.11.2
kernel: 4.15

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #20 from bugreporte...@gmail.com ---
Following up on my last comment, the issue seems to have gotten a bit worse
after 18.08.2.

I used to leave Dolphin open for days and weeks at a time, with a number of
tabs set up for longer term tasks. Now that I have to close Dolphin several
times a day to keep it responsive, I see that Dolphin would benefit from
saved/named sessions like those found in Kate.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Patrice Grundmann]

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

Patrice Grundmann  changed:

   What|Removed |Added

 CC||patrice.grundm...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Reuben]

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

Reuben  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

bugreporte...@gmail.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #19 from bugreporte...@gmail.com ---
I am running Dolphin 18.08.1 on Arch Linux. The problem still exists for me. To
reproduce, let Dolphin stay open for a few days. Then add or remove a bookmark
in the Places panel. Dolphin will freeze for several minutes.

There are other symptoms of Dolphin being much slower than it was prior to the
changes that were made a couple months before I first reported this issue.
However, this bookmark test is an easy one to quantify. Previously, there was
essentially no delay. Now, adding a bookmark makes Dolphin unresponsive for
several seconds, and if Dolphin has been left open for a few days, that delay
increases to several minutes.

I may have more bookmarks in Dolphin than some people, but it is not an
unreasonable number. Back on May 8, we discussed the size of my
~/.local/share/user-places.xbel file. It is currently 1192 lines.

Anything else I can tell you?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Andrew Crouthamel]

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

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #18 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 Resolution|LATER   |WAITINGFORINFO

--- Comment #17 from Julian Schraner  ---
18.08 has been released for about a month now. Have you been able to update
Dolphin and test this again? It'd be great to know if you do still experience
this issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||juliquad...@gmail.com
 Resolution|--- |LATER

--- Comment #16 from Julian Schraner  ---
There have been various memory leaks that were fixed just this week, so it'd be
great if you could test again after the release of KDE Applications 18.08 (16th
of August). For now, I'll set this report to NEEDSINFO/LATER.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #15 from bugreporte...@gmail.com ---
I went ahead and closed Dolphin and reopened it. After that, pmap reports the
following memory usage:

total 853220K

That's down from this amount just before I closed & reopened it:
total 5551616K

That's a reduction of 4698396 or around 4.5 GB. This is my guess: it looks like
Dolphin memory usage grows by 1 GB per day on average and that after a couple
days the UI becomes very sluggish.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #14 from bugreporte...@gmail.com ---
On Mon, Jun 4, 2018 at 4:51 PM, Elvis Angelaccio 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=393977
>
> --- Comment #13 from Elvis Angelaccio  ---
> Hmm, what's your usual workflow? Do you open a lot of tabs/windows with
> many
> files?
>

Thanks for following up. I do not do anything differently than I have done
for the last ten years of using Dolphin. This behavior started a few months
ago. I certainly do not "max out" Dolphin in any way. I generally use it
only with a couple tabs open. I demand a lot more of Kate, for example,
where I keep large projects open all the time. I would say I use Dolphin
lightly.

BTW, I love Dolphin. I think it is the best file manager on Linux. I'm not
here to bash Dolphin. I'm just motivated to provide any feedback I can
regarding this issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Elvis Angelaccio]

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

--- Comment #13 from Elvis Angelaccio  ---
Hmm, what's your usual workflow? Do you open a lot of tabs/windows with many
files?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #12 from bugreporte...@gmail.com ---
One day later and now Dolphin is using over 5 GB of RAM. Specifically, pmap
shows "total 5551616K"

Is any other information required? If not, I will close and reopen Dolphin to
free up all this memory and get Dolphin back to running snappy.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #11 from bugreporte...@gmail.com ---
Here's an update. The Dolphin GUI has gotten very sluggish now (after
letting Dolphin run several days without closing it). However, there are no
unusual messages in gdb. Right now, copying a file from one file pane to
the other exhibits a very slow GUI, but there are zero debug messages
associated with this action. Any suggestions for next steps? Does the pmap
output below help? (As I mentioned, this GUI slowness is relatively new. I
first notice it a couple months ago after using Dolphin for more than 10
years.)

$ pmap 33240
33240:   /usr/bin/dolphin
4000  4K r-x-- dolphin
55754000  4K r dolphin
55755000  4K rw--- dolphin
55756000 2308240K rw---   [ anon ]
7fff6c00132K rw---   [ anon ]
7fff6c021000  65404K -   [ anon ]
7fff7000132K rw---   [ anon ]
7fff70021000  65404K -   [ anon ]
7fff7400132K rw---   [ anon ]
7fff74021000  65404K -   [ anon ]
7fff7800132K rw---   [ anon ]
7fff78021000  65404K -   [ anon ]
7fff7c00132K rw---   [ anon ]
7fff7c021000  65404K -   [ anon ]
7fff8400132K rw---   [ anon ]
7fff84021000  65404K -   [ anon ]
7fff8800132K rw---   [ anon ]
7fff88021000  65404K -   [ anon ]
7fff8c00132K rw---   [ anon ]
7fff8c021000  65404K -   [ anon ]
7fff9000132K rw---   [ anon ]
7fff90021000  65404K -   [ anon ]
7fff9400132K rw---   [ anon ]
7fff94021000  65404K -   [ anon ]
7fff9800132K rw---   [ anon ]
7fff98021000  65404K -   [ anon ]
7fff9c00132K rw---   [ anon ]
7fff9c021000  65404K -   [ anon ]
7fffa000276K rw---   [ anon ]
7fffa0045000  65260K -   [ anon ]
7fffa400132K rw---   [ anon ]
7fffa4021000  65404K -   [ anon ]
7fffa8069000  4K -   [ anon ]
7fffa806a000   8192K rwx--   [ anon ]
7fffa886a000  4K -   [ anon ]
7fffa886b000   8192K rwx--   [ anon ]
7fffa986c000  4K -   [ anon ]
7fffa986d000   8192K rwx--   [ anon ]
7fffaa86e000  4K -   [ anon ]
7fffaa86f000   8192K rwx--   [ anon ]
7fffab06f000 52K r-x-- extracthere.so
7fffab07c000   2048K - extracthere.so
7fffab27c000  4K r extracthere.so
7fffab27d000  4K rw--- extracthere.so
7fffab27e000236K r-x-- libnss_systemd.so.2
7fffab2b9000   2044K - libnss_systemd.so.2
7fffab4b8000 12K r libnss_systemd.so.2
7fffab4bb000  4K rw--- libnss_systemd.so.2
7fffab4bc000244K r-x-- libnss_mymachines.so.2
7fffab4f9000   2044K - libnss_mymachines.so.2
7fffab6f8000 12K r libnss_mymachines.so.2
7fffab6fb000  4K rw--- libnss_mymachines.so.2
7fffab8e2000108K r-x-- KF5WindowSystemX11Plugin.so
7fffab8fd000   2048K - KF5WindowSystemX11Plugin.so
7fffabafd000  8K r KF5WindowSystemX11Plugin.so
7fffabaff000  4K rw--- KF5WindowSystemX11Plugin.so
7fffabb0 20K r-x-- extractfileitemaction.so
7fffabb05000   2044K - extractfileitemaction.so
7fffabd04000  4K r extractfileitemaction.so
7fffabd05000  4K rw--- extractfileitemaction.so
7fffabd06000 80K r-x-- bluetoothfileitemaction.so
7fffabd1a000   2048K - bluetoothfileitemaction.so
7fffabf1a000  4K r bluetoothfileitemaction.so
7fffabf1b000  4K rw--- bluetoothfileitemaction.so
7fffabf1c000 12K r-x-- baloofilepropertiesplugin.so
7fffabf1f000   2048K - baloofilepropertiesplugin.so
7fffac11f000  4K r baloofilepropertiesplugin.so
7fffac12  4K rw--- baloofilepropertiesplugin.so
7fffac121000   1076K r-x-- libsqlite3.so.0.8.6
7fffac22e000   2048K - libsqlite3.so.0.8.6
7fffac42e000 20K r libsqlite3.so.0.8.6
7fffac433000  8K rw--- libsqlite3.so.0.8.6
7fffac435000  4K rw---   [ anon ]
7fffac436000 64K r-x-- libqsqlite.so
7fffac446000   2048K - libqsqlite.so
7fffac646000  4K r libqsqlite.so
7fffac647000  4K rw--- libqsqlite.so
7fffac648000  8K r-x-- libutil-2.27.so
7fffac64a000   2044K - libutil-2.27.so
7fffac849000  4K r libutil-2.27.so
7fffac84a000  4K rw--- libutil-2.27.so
7fffac84b000 40K r-x-- libKF5Pty.so.5.45.0
7fffac855000   2044K - libKF5Pty.so.5.45.0
7fffaca54000  4K r libKF5Pty.so.5.45.0
7fffaca55000  4K rw--- libKF5Pty.so.5.45.0
7fffaca56000620K r-x-- libkerfuffle.so.18.4.0
7fffacaf1000   2048K - libkerfuffle.so.18.4.0
7fffaccf1000 28K r libkerfuffle.so.18.4.0
7fffaccf8000  4K rw--- libkerfuffle.so.18.4.0
7fffaccf9000 20K r-x-- compressfileitemaction.so
7fffaccfe000   2044K - 

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #10 from bugreporte...@gmail.com ---
On Fri, Jun 1, 2018 at 5:04 PM, Elvis Angelaccio 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=393977
>
> --- Comment #9 from Elvis Angelaccio  ---
> (In reply to bugreporter11 from comment #8)
> > Is this the right method for running Dolphin from gdb?
> > $ gdb dolphin 2>&1 | tee dolphin.gdb
> > (gdb) run
> > Starting program: /usr/bin/dolphin
>
> Yes, that should work.
>
>
> In my experience, the GUI gets slower and slower over time when I leave
Dolphin open. Prior to a few months ago, this did not happen. I would leave
Dolphin open for weeks (or months) at a time on my desktop computer. Since
a change a few months ago, I now close Dolphin each night. This keeps the
GUI acting relatively responsively.

For this test, I have been running Dolphin from gdb for two days without
closing it. Today I can notice a slight decrease in GUI responsiveness
(very slight), but the messages in gdb are exactly the same. There are no
additional error messages or anything that looks abnormal.

I'll continue this for another week or so and see if any messages change
and how much Dolphin slows down over time.

So far the messages I see are similar to these. There are not many of these:

Empty filename passed to function
kf5.kservice.services: KMimeTypeTrader: mimeType "" not found

inotify_add_watch("/home/user/Downloads/MyTemp") failed: "Permission denied"
org.kde.knotifications: Audio notification requested, but sound file from
notifyrc file was not found, aborting audio notification

Access to ' "/home/user/workspaces/xyz" ' denied, not owned by root,
executable flag not set.

UdevQt: unhandled device action "bind"
UdevQt: unhandled device action "unbind"

And only one message like each of these:
Trying to convert empty KLocalizedString to QString.
qt.accessibility.core: Cannot create accessible child interface for
object:  PlacesView(0x558f33a0)  index:  41

Other than that, the messages are mostly like this:

[New Thread 0x7fff81ffb700 (LWP 15125)]
[Thread 0x7fff81ffb700 (LWP 15125) exited]
org.kde.dolphin: Saving view-properties to ...

I would like to fix the permission issues and other issues, but I don't see
anything wrong with any permissions. I own the directories mentioned in the
messages. And I'm sure these messages are not related to the slow GUI
responsiveness issue I am troubleshooting now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Elvis Angelaccio]

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

--- Comment #9 from Elvis Angelaccio  ---
(In reply to bugreporter11 from comment #8)
> Is this the right method for running Dolphin from gdb?
> $ gdb dolphin 2>&1 | tee dolphin.gdb
> (gdb) run
> Starting program: /usr/bin/dolphin

Yes, that should work.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #8 from bugreporte...@gmail.com ---
see below

On Sat, May 19, 2018 at 5:45 AM, Elvis Angelaccio 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=393977
>
> Please start dolphin from gdb and press CTRL+C when it gets stuck. Then
> copy
> here the stacktrace from gdb.
>

Is this the right method for running Dolphin from gdb?
$ gdb dolphin 2>&1 | tee dolphin.gdb
(gdb) run
Starting program: /usr/bin/dolphin

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Elvis Angelaccio]

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

--- Comment #7 from Elvis Angelaccio  ---
(In reply to bugreporter11 from comment #6)
> As another test, I have left Dolphin open for the last two days. Now
> clicking on any GUI element shows several seconds of delay and refreshing
> the file panes is very slow.
> 
> "top" shows high CPU usage for Dolphin in response to these routine GUI
> actions. Closing Dolphin causes 100% CPU usage for several seconds.
> 
> After reopening Dolphin, normal responsiveness returns for most actions (but
> not for bookmarks in the Places panel).

Please start dolphin from gdb and press CTRL+C when it gets stuck. Then copy
here the stacktrace from gdb.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #6 from bugreporte...@gmail.com ---
As another test, I have left Dolphin open for the last two days. Now clicking
on any GUI element shows several seconds of delay and refreshing the file panes
is very slow.

"top" shows high CPU usage for Dolphin in response to these routine GUI
actions. Closing Dolphin causes 100% CPU usage for several seconds.

After reopening Dolphin, normal responsiveness returns for most actions (but
not for bookmarks in the Places panel).

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from Nate Graham  ---
Thanks for all the testing!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #4 from bugreporte...@gmail.com ---
see reply inline

On Tue, May 8, 2018 at 7:48 PM, Bug Reporter 
wrote:

> see reply inline
>
> On Tue, May 8, 2018 at 2:51 PM, Nate Graham 
> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=393977
>>
>> Nate Graham  changed:
>>
>>What|Removed |Added
>> 
>> 
>>  Status|UNCONFIRMED |NEEDSINFO
>>  Resolution|--- |WAITINGFORINFO
>>
>> --- Comment #2 from Nate Graham  ---
>> On the affected machines, is ~/.local/share/user-places.xbel incredibly
>> long?
>> Like, 1000+ lines long?
>>
>
> Yes, on my machine this file is 1415 lines long. A good portion of that
> length is due to devices that are added automatically by the system. I
> don't use those or even want them shown in Dolphin's Places.
>
> Can I manually edit ~/.local/share/user-places.xbel to remove all the
> devices I don't want? (Dolphin doesn't provide the option to remove them,
> only to hide them.)
>
> Thanks
>

I experimented. I edited ~/.local/share/user-places.xbel to remove all the
automatically added or obsolete entries and the file was reduced to about
650 lines. I opened Dolphin and moved one bookmark up one place in the
Places list. Even with the smaller file, the operation was still slow
(requiring about 3 seconds to complete). After this simple operation,
~/.local/share/user-places.xbel increased to 997 lines and many of the
entries I had removed were restored.

The automatically restored entries are all of this type:

 
  
   http://www.kde.org;>
/org/kde/fstab/
true
false
   
   http://freedesktop.org;>

   
  
  ... on server
 

I do not need any of those in Places. These include 20 automatically added
"Remote devices" and 7 "Devices". I have 35 of my own bookmarks and those
are all I need.

After the first test, repeated tests (moving a bookmark in Places)  also
require about 3 seconds. (Until a recent Dolphin change a few weeks ago,
this operation was nearly instant.) The file ~/.local/share/user-places.xbel
remains at 997 lines after these repeated tests, as I'm sure you would have
expected.

Adding or removing bookmarks in Places is not the only function that is
slow now. I experience extensive slowness with operations in the file panes
under some circumstances. However, so far I am unable to give exact steps
to reproduce it. It seems to happen when I have had Dolphin open all day.

Hope that info helps. Thank you. Dolphin is the best Linux file manager!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #3 from bugreporte...@gmail.com ---
see reply inline

On Tue, May 8, 2018 at 2:51 PM, Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=393977
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
> 
>  Status|UNCONFIRMED |NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>
> --- Comment #2 from Nate Graham  ---
> On the affected machines, is ~/.local/share/user-places.xbel incredibly
> long?
> Like, 1000+ lines long?
>

Yes, on my machine this file is 1415 lines long. A good portion of that
length is due to devices that are added automatically by the system. I
don't use those or even want them shown in Dolphin's Places.

Can I manually edit ~/.local/share/user-places.xbel to remove all the
devices I don't want? (Dolphin doesn't provide the option to remove them,
only to hide them.)

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Nate Graham  ---
On the affected machines, is ~/.local/share/user-places.xbel incredibly long?
Like, 1000+ lines long?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[bugzilla_noreply]

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

--- Comment #1 from bugreporte...@gmail.com ---
We have 12 desktops running the latest version of KDE / Plasma / Dolphin from
the Arch Linux repos. All are currently on dolphin 18.04.0. Today I went around
to several of those desktops and I can report a new observation. Those without
any bookmarks in the Places panel seem to respond quickly when adding a new
bookmark or moving a bookmark. But those with a larger number of existing
bookmarks exhibit slowness both when adding a new bookmark and when moving an
existing bookmark up or down the order within Places. This slowness is new with
a recent update. My sample size is small, but it does confirm that the issue is
not limited to a single computer. Does this warrant changing the status to
confirmed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 393977] Dolphin has become very slow after recent update

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.