Dolphin takes a long time to reinitialise when it last had a `fish://` tab open that points to an unavailable host

Development
1

The last time this occurred, it actually became entirely stuck, to the extent that not even a SIGKILL could kill it, demonstrating to me that it’s doing something low-level:

A lesser version recurs now, [1] so I’ve run it through strace, and it shows readlink("/run/user/1000/kio-fuse-urGFsO/fish/RokeJulianLockhart@192.168.1.123/home/RokeJulianLockhart", 0x7ffc3981ac50, 1023) = -1 EINVAL (Invalid argument) for almost all of the time that I’m waiting:

#!/usr/bin/env sh
strace -T $(command -v dolphin)

0.000102 readlink("/run/user/1000/kio-fuse-urGFsO/fish/RokeJulianLockhart@192.168.1.123", 0x7fff5a7a37c0, 1023) = -1 EINVAL (Invalid argument) <0.000029>
0.000040 readlink("/run/user/1000/kio-fuse-urGFsO/fish/RokeJulianLockhart@192.168.1.123/home", 0x7fff5a7a37c0, 1023) = -1 EINVAL (Invalid argument) <3.085690>
3.085728 readlink("/run/user/1000/kio-fuse-urGFsO/fish/RokeJulianLockhart@192.168.1.123/home/RokeJulianLockhart", 0x7fff5a7a37c0, 1023) = -1 EINVAL (Invalid argument) <6.144062>
6.144652 write(5, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000017>

Because it’s so reproducible, I managed to capture a perf record --call-graph dwarf dolphin, and hotspot produces what looks like a flamegraph with an interesting spike (when it works): [2]

1661×2907 232 KB

…Is any of this of any use?

  1. bugzilla.redhat.com/show_bug.cgi?id=2367021 ↩︎

  2. bugzilla.redhat.com/show_bug.cgi?id=2367022 ↩︎

2

For what it’s worth, this seems like one of these issues?

2 Likes
3

@johnandmegh, that looks more like:

Perhaps, I should ask them whether that issue should be resolved as KDE’s problem.

That sounds a lot like this, except that for them, it appears to consistently crash. Perhaps because they’re disconnecting the mount whilst Dolphin is open, rather than connecting to it when it’s already disconnected? That would explain it hung nigh endlessly for me the first time – when I actively disconnected it.

Thanks. I’ll ask them what they think of this. [1]

  1. bugs.kde.org/show_bug.cgi?id=423187#c20 ↩︎

4

Upload svg for flamegraphs.

Raster images are illegible for image with such text details, with svg you can always zoom in to see the text.

1 Like
5

@meven, apologies: I was lazy because Discourse seemed to reject my SVGs. I’m surprised you allow people to upload ≥ 50 MiB bitmaps, yet reject mere ≤ 500 KiB-equivalent vectors. Seems like a poor use of storage.

I was going to upload perf’s .data, and the SVG, to NextCloud, but Collaborate is HTTP 500, so hopefully MediaFire is acceptable: