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

            Bug ID: 465270
           Summary: Plasma freezes or becomes very slow when there's heavy
                    IO
    Classification: Plasma
           Product: kwin
           Version: 5.26.90
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 155935
  --> https://bugs.kde.org/attachment.cgi?id=155935&action=edit
KDiskMark using a test folder on the Desktop for its work files

SUMMARY
Plasma freezes or becomes very slow when there's heavy IO


STEPS TO REPRODUCE
1. Download KDiskMark from
https://github.com/JonMagon/KDiskMark/releases/tag/3.1.2
2. Install Gdebi with: sudo apt install gdebi
3. Install KDiskMark with: sudo gdebi kdiskmark_3.1.2-ubuntu_amd64.deb
4. Create a folder on the Desktop, for example "Disk-test"
5. Open KDiskMark utility
6. From its 3rd configuration field (second drop-down) choose "Add a directory"
and select previously created "Disk-test" or whatever named you decided to use.
7. Click on the "All" button to start testing the disk where KDE Plasma is
installed
8. With this disk testing utility is running in background, try to do anything
you would normally do

OBSERVED RESULT
As the disk benchmark utility runs in background, potentially creating a lot of
Input / Output requests to the same disk that Plasma is using, I see that the
desktop either freezes (becomes completely unresponsive), not being able to use
even the mouse, or the effects of actions are delayed a lot.
So clicking on the start menu, clock widget, trying to open Dolphin, Kate,
Konsole, System Settings seems to not be that responsive as it takes a lot of
time until they open.
Navigating the System Settings by clicking on different menu items also takes a
lot of time

EXPECTED RESULT
I expect that Plasma doesn't freeze no matter how much IO is in the background.
If it somehow needs to freeze, I expect that at least the mouse can be moved so
I can move it where I want it to be next and click something that may not
respond at that time, but that action will still be queued for when Plasma
becomes responsive again so I don't just stay doing absolutely nothing.

Another thing that I expect is that at least the most common and used apps,
like Dolphin, Kate, Konsole, Gwenview will be always available with no delay.

If one of them is open at that time and I'm doing something in it, like writing
some text in Kate, I expect that the writing action will not be disturbed no
matter how much IO is in the background.

Same for GwenView, I zoom in or out at the time, that has nothing to do with
the disk, this action should not be disturbed by the heavy IO.

I expect that the RAM memory is better utilized is I don't need so much free
memory if the desktop freezes or slows down, which makes me lose time.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
If the freezes or slow downs of Plasma are not reproducible or not really
obvious with KDiskMark running in the back, please try the following:
Use KDE Plasma from a HDD
Or from a USB flash drive
Or from a USB flash drive, but with a persistence file enable, like in my test
(Lexar USB flash drive + 4GiB persistence file)

A USB flash drive + persistence file + KDiskMark running in background should
make this problem really obvious.

I know that this looks like an edge case, but I intentionally decided to use
the persistence file and KDiskMark at the same time to make it much more easily
reproducible.

As both the freezes and slow down happened to me in the past even when I was
using the internal memory.

At that time when it happened, I was using BTRFS or BTRFS + Zstd compression.

And when I was compressing / extracting many files from archives or I was
copying / moving folders with many items inside from one place to another.

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

Reply via email to