[ark] [Bug 445947] New: Premature failure (notified as success) of archive extraction when last dolphin file manager closed.
https://bugs.kde.org/show_bug.cgi?id=445947 Bug ID: 445947 Summary: Premature failure (notified as success) of archive extraction when last dolphin file manager closed. Product: ark Version: 21.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: thomwalker...@mail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Premature failure (notified as success) of archive extraction when last dolphin file manager closed. **Potentially**? an actual issue with Kio? But not 100% sure. Could be wrong, as it's the only connection between dolphin and ark, unless I'm wrong. STEPS TO REPRODUCE 1. Open one dolphin instance. Make sure no other instances are running (window instances). 2. Attempt two [my case] (or one) large extraction (40GB+ files) with ark using the "autodetect directory" option to have parent directory hold the same name as the archive. Watch as dolphin notification on the right hand side provides an "extracting files" feedback. 3. Close dolphin window (making sure this window you close is the last one running). OBSERVED RESULT The notifications on the right hand side suddenly change to "Finished" (successfully?) even though it is obvious the 40GB files did not finish extracting. Ark seems to exit at that point. Extract files are partially lying around. EXPECTED RESULT Ark should continue extracting. There should be no dependency between Ark and dolphin, the file manager. Let alone, interacting with dolphin to affect an archive extraction. SOFTWARE/OS VERSIONS OS: Manjaro Linux x86_64 Host: TUF Gaming FX505DY_FX505DY 1.0 Kernel: 5.15.2-2-MANJARO Uptime: 21 hours, 34 mins Packages: 1825 (pacman), 7 (flatpak) Shell: bash 5.1.8 Resolution: 1920x1080 DE: Plasma 5.23.3 WM: KWin Theme: Breeze Light [Plasma], Breeze [GTK2/3] Icons: breeze [Plasma], breeze [GTK2/3] Terminal: konsole Terminal Font: Monospace 11 CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8) @ 2.100GHz GPU: AMD ATI 05:00.0 Picasso GPU: AMD ATI Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X Memory: 11821MiB / 15749MiB KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Using X11. ADDITIONAL INFORMATION Likely not useful, but for completionist's sake: * My extraction was occurring on an external hdd. * I had four torrenting operations (qBittorrent) running with over 15MB/s throughput writing to the same HDD, elsewhere on a partition. Basically, high IO. No, this isn't the issue because instead of closing dolphin windows, I minimized them. The extractions continued as normal. (under the same circumstances/scenario) * Not running out of disk space. I had 612GB free on the partition I was extracting to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441551] plasmashell leaks memory over time
https://bugs.kde.org/show_bug.cgi?id=441551 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #3 from Quartz --- Bump x9. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432449] Memleak in plasmashell 5.20.5
https://bugs.kde.org/show_bug.cgi?id=432449 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #20 from Quartz --- Bump x7. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436119] Possible memory leak
https://bugs.kde.org/show_bug.cgi?id=436119 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #5 from Quartz --- Bump x6. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #13 from Quartz --- Bump x5. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430139] plasmashell has a memory leak
https://bugs.kde.org/show_bug.cgi?id=430139 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #7 from Quartz --- Bump x4. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #9 from Quartz --- Bump x3. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak
https://bugs.kde.org/show_bug.cgi?id=393929 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #29 from Quartz --- Bump x2. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414132] Plasma 5.12 causes memory leak in Xorg not freeing pixmap memory
https://bugs.kde.org/show_bug.cgi?id=414132 Quartz changed: What|Removed |Added CC||thomwalker...@mail.com --- Comment #7 from Quartz --- Bump. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 --- Comment #6 from Quartz --- Aye. I'm going to do some more isolation... After about a good few hours, I've eliminated the widgets so it seems the widgets themselves aren't leaking. I'm left now with the following culprits. I will do some more testing. It's not easy to grab metrics every 3-4 hours... Anyway, I've killed almost everything on my system and these were left, still occupying that huge chunk of memory: POSIBBLE LEAKERS * kglobalaccel5 * kdeinit5 * kf5/start_kde * sddm * polkitd * dbus (some service?) * systemd (some script)? * ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 --- Comment #4 from Quartz --- If it helps, I've also changed my update tick time to 2 seconds rather than the "No Limit" option as the rendering updated too fast for my liking. Attempt this as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 --- Comment #3 from Quartz --- Created attachment 142638 --> https://bugs.kde.org/attachment.cgi?id=142638&action=edit Memory after boot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 --- Comment #2 from Quartz --- Created attachment 142637 --> https://bugs.kde.org/attachment.cgi?id=142637&action=edit Memory leak at time of issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 Quartz changed: What|Removed |Added Keywords||efficiency, reproducible, ||Tracking --- Comment #1 from Quartz --- X server used. Not wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444062] New: Severe widget memory leak - one or many, perhaps all.
https://bugs.kde.org/show_bug.cgi?id=444062 Bug ID: 444062 Summary: Severe widget memory leak - one or many, perhaps all. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: thomwalker...@mail.com Target Milestone: 1.0 SUMMARY There is an anomaly with the amount of RAM usage/accumulation after a several amount of time the plasma widgets are being used for. After 4 hours of uptime, I have observed (after closing down my other applications, other than plasma-widgets, about 7-8GB of RAM being eaten by metrics accumulated by widgets. Please see screenshot. STEPS TO REPRODUCE 1. Open at least 6-8 types of widgets for metrics such as seen in the screenshot. 2. Wait 5+ hours. 3. Use the machine as per usual. OBSERVED RESULT Leaked memory and high RAM usage coming from a large array of kdeplasmashell processes. After reboot, things went to normal. Reproduceable. EXPECTED RESULT Metrics/widgets should release/clear memory if it has accumulated a certain amount of it. RAM should have been 1.1GB (the norm for my machine when having nothing running other than the shell/system). Not 8.2GB. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.19-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 15.3 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #3 from Quartz --- ** This issue also occurs on the Task Manager (not just the icons only widget) taskbar widget when items are grouped. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #2 from Quartz --- Machine is not thrashing or under performance load for this to occur. It occurs under normal circumstances. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 --- Comment #1 from Quartz --- Workflow, especially with multiple windows gets slowed down and gives overall poor usability and experience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 Quartz changed: What|Removed |Added Keywords||accessibility, efficiency, ||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444001] New: Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows.
https://bugs.kde.org/show_bug.cgi?id=444001 Bug ID: 444001 Summary: Performance stagger in animation and rendering when hovering over grouped Icons-Only Task Manager; given that the grouped windows contain more than 3-5 windows. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: thomwalker...@mail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When having more than 3-5 windows (of the same type) open on the taskbar and they get grouped together [such as 15 firefox windows minimized]... ...shine hover animation becomes evidently and noticeably impacted framerate wise and the cursor, as well as the icon itself starts to stagger. STEPS TO REPRODUCE 1. Open 10, 20 or more windows of the same program (in my case, it was firefox) 2. Let them group. 3. While having other running programs, attempt to hover left and right between each and observe what happens when going over the program with lots of grouped windows. OBSERVED RESULT Slow, staggered animation, possibly even slowed cursor? Unnatural animation transition. Becomes an annoyance when working with multiple windows. EXPECTED RESULT Smooth animation transition between icons on the taskbar without staggering. SOFTWARE/OS VERSIONS OS: Manjaro Linux x86_64 Host: TUF Gaming FX505DY_FX505DY 1.0 Kernel: 5.13.19-2-MANJARO Uptime: 3 hours, 23 mins Packages: 1548 (pacman), 4 (flatpak) Shell: bash 5.1.8 Resolution: 1920x1080 DE: Plasma 5.22.5 WM: KWin Theme: Breath2 2021 Light [Plasma], Breeze [GTK2/3] Icons: [Plasma], breath2 [GTK2/3] Terminal: konsole CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8) @ 2.100GHz GPU: AMD ATI 05:00.0 Picasso GPU: AMD ATI Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X Memory: 11126MiB / 15688MiB KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Compositor is off/disabled. GPU drivers are installed. -- You are receiving this mail because: You are watching all bug changes.
