https://bugs.kde.org/show_bug.cgi?id=462675
Steve Vialle <stev...@runbox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Version|22.08.3 |24.08.3
CC| |stev...@runbox.com
Status|REPORTED |CONFIRMED
--- Comment #3 from Steve Vialle <stev...@runbox.com> ---
Marking confirmed and bumping version, as I can still trivially reproduce this
behaviour in recent (24.08.3) builds, with a fast (~1000MiB/s) NFS mount, a
slow (~130MiB/s) mechanical drive, and a garden-variety SD card.
Any operation that saturates I/O on a device, causes a drive to spin up, or
touches a high-latency filesystem of any kind causes dolphins UI to freeze.
i.e. perfectly ordinary usage rendering the UI borderline unusable.
There are countless related bug reports on the tracker, and for some reason
https://bugs.kde.org/show_bug.cgi?id=423187 appears to be the only one
receiving any attention whatsoever... Despite being 4 years old and initially
specific to network mounts.
It's all the same problem though: IOPS are finite, filesystem latency is
variable, and interactive UI threads shouldn't be blocking on I/O...
*especially* I/O initiated by simply using the file-manager for its intended
purpose. That's a horrible UX no matter how you slice it, and no amount of
helpful "filesystem not responding" notifications or suggestions to use
FUSE/KIOslaves for everything are going to solve it.
--
You are receiving this mail because:
You are watching all bug changes.
