[dolphin] [Bug 418489] Dolphin xdg folder paths do not match with ones in plasma settings
https://bugs.kde.org/show_bug.cgi?id=418489 Fabian Otto changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- CC||fabian_otto...@yahoo.de Platform|Ubuntu |openSUSE Version|19.04.3 |23.04.0 --- Comment #4 from Fabian Otto --- I'd like to re-open this bug as while the behaviour described in the original report remains unchanged this seems to be working flawlessly in the flatpak version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432449] New: Memleak in plasmashell 5.20.5
https://bugs.kde.org/show_bug.cgi?id=432449 Bug ID: 432449 Summary: Memleak in plasmashell 5.20.5 Product: plasmashell Version: 5.20.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: fabian_otto...@yahoo.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Memleak on openSUSE Tumbleweed. Keeps increasing RES STEPS TO REPRODUCE 1. Start plasma desktop and check RES in htop 2. wait a few hours. Normal activity 3. check again for RES in htop OBSERVED RESULT RES has more than doubled in size. Biggest observed yet: around 1400MB EXPECTED RESULT RES is the same as when it was started. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.20.5 / openSUSE Tumbleweed 20210131 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- 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 --- Comment #2 from Fabian Otto --- (In reply to Nate Graham from comment #1) > What's the process that's increasing in memory use? plasmashell itself. This was on wayland btw. -- 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 --- Comment #19 from Fabian Otto --- (In reply to David Edmundson from comment #18) > I went through heaptrack, thanks. > > All leaks and peak usage are inside mesa in the Intel driver (unfortunately > exact locations within mesa are unresolved) > > This /could/ still mean plasma or Qt is at fault missing some GL calls to > remove textures, but it seems unlikely given we claim it came in for 5.20.5 > and I can't think of anything changed in plasma in there. > > Most likely this points to a driver bug. > If you are in a position to upgrade/downgrade mesa that would really help. I did go through the heaptrack as well, what made me question whether it's actually a driver bug though is twofold: 1. It's not a problem on Xorg 2. GNOME Wayland should use the same calls if it IS a Vulkan or OpenGL driver implementation thing. So if that was the case GNOME's memory usage should go up too. It does not however. So either there is a call being used or not being that GNOME simply does not touch or it's something else. Then again I'm not a programmer and this is just conjecture on my part. My reasoning might be flawed. As for it starting in 5.20.5 it could not swear on it, that was just when I first took notice of it. Might have been introduced earlier than that. -- 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 Fabian Otto changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Fabian Otto --- (In reply to Nate Graham from comment #7) > Can you get a heaptrack log? here you go. Heaptrack of plasmashell 5.21.1 but same problem still. https://mega.nz/file/hPxk0ZyC#0GA7VZh0OdkRsydChjollNYAMJoKgaM9ol-4n_V6QWw -- 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 --- Comment #13 from Fabian Otto --- (In reply to David Edmundson from comment #11) > Framegraph shows two distinct areas of usage at peak: > - Appstream (150Mb) > - Your graphic drivers (300Mb) > > Neither of which seem ideal. > > > Can you confirm that krunner also spirals out of control after doing a query? > and if you get high usage in systemsettings5 I can confirm, that krunner too also starts to memleak after doing a query. Heaptrackfile for it here: https://mega.nz/file/cPxEiY4S#zWyWEXuuxAZ0m48b-ErL0ub2lG239skJWjgBef23RyU ``` total runtime: 74.23s. calls to allocation functions: 8103421 (109173/s) temporary memory allocations: 539318 (7265/s) peak heap memory consumption: 101.37MB peak RSS (including heaptrack overhead): 272.14MB total memory leaked: 98.78MB ``` As for systemsettings5 I do not get high resource usage here. Neither in RAM nor CPU. -- 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 --- Comment #14 from Fabian Otto --- (In reply to Vlad Zahorodnii from comment #12) > Do you use any third party wallpaper plugin? Also, the provided archive file > seems corrupted > > plasmashell.5011.zst : 124 MB... plasmashell.5011.zst : Read error (39) > : premature end I do not use anything third party. Only what came with the package. Also here is a new heaptrack file. No idea why the last one had problems for you. See also my reply to David Edmundson for the heaptrack file for krunner. https://mega.nz/file/QXhQXaJI#P0sthT8xFG7FU8ZyVYuXYogD1-Yko9vfdqt8dvz495s -- 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 --- Comment #5 from Fabian Otto --- (In reply to David Edmundson from comment #4) > This doesn't have enough information to act on. > > Please test removing widgets or get a heaptrack log. There are no widgets installed besides the default ones. The used theme is unmodified Breeze Dark. The Problem only exists in wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417569] New: GDK_BACKEND=wayland is being set globally. It should not
https://bugs.kde.org/show_bug.cgi?id=417569 Bug ID: 417569 Summary: GDK_BACKEND=wayland is being set globally. It should not Product: plasmashell Version: 5.17.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: fabian_otto...@yahoo.de Target Milestone: 1.0 SUMMARY GDK_BACKEND=wayland is being set globally. It should not. Leads to X11 only apps not working. STEPS TO REPRODUCE 1. open application that is x11-only like Discord OBSERVED RESULT Application won't start EXPECTED RESULT Application starts SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17.5 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Distro: openSUSE Tumbleweed ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
