Bug 426022 - Dolphin crashes if the drive's throughput is saturated
Summary: Dolphin crashes if the drive's throughput is saturated
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 20.08.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2020-08-31 15:49 UTC by twinshadows404
Modified: 2020-09-10 07:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
SSD to HDD crash (3.10 KB, text/plain)
2020-08-31 15:49 UTC, twinshadows404
Details
USB3.0 to HDD crash (9.31 KB, text/plain)
2020-08-31 15:49 UTC, twinshadows404
Details

Note You need to log in before you can comment on or make changes to this bug.
Description twinshadows404 2020-08-31 15:49:06 UTC
Created attachment 131317 [details]
SSD to HDD crash

SUMMARY
Copying files from faster drives to slower ones, maxes out their throughput and causes Dolphin to crash if you try to browse folders on the slower drive. 
reproducibility: always
Bugs which might have the same root cause: 208888, 411213, 410760

STEPS TO REPRODUCE
1. Copy something from a faster drive to a slower
2. Try to browse folders on the slower drive

OBSERVED RESULT
Dolphin crashes

EXPECTED RESULT
Dolphin remains useable

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20200826
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.2-1-default
OS Type: 64-bit
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 15,6 GiB of RAM

ADDITIONAL INFORMATION
Copying from an SSD or 3.0 USB to HDD causes a crash, however copying from 2.0 USB to HDD doesn't.
Both the SSD and the USB remain useable during copying, but browsing the HDD crashes
Comment 1 twinshadows404 2020-08-31 15:49:39 UTC
Created attachment 131318 [details]
USB3.0 to HDD crash
Comment 2 Elvis Angelaccio 2020-08-31 17:12:43 UTC
> The Wayland connection broke. Did the Wayland compositor die

Can you try on X11? This doesn't look IO-related.
Comment 3 twinshadows404 2020-08-31 18:17:40 UTC
It doesn't crash on X11, but it's very sluggish.
On wayland the compositor doesn't die, just dolphin
Comment 4 Christoph Feck 2020-09-10 07:58:32 UTC
The reason is that UI queues aren't working fast enough, so Wayland thinks the connection broke. X11 handles this situation better. I suggest to report this to QtWayland developers; they may know which component in the Wayland stack needs improvements.