[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #71 from LucasGGamerM --- I have noticed something weird about this bug. After unplugging and plugging my monitors back in, kwin only happens to leak memory (for me) when moving the mouse on a monitor directly connected to the nvidia gpu, and it also comes with momentary cpu usage spikes (to 20-30% usage from a normal 5%). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 LucasGGamerM changed: What|Removed |Added OS|Linux |All CC||lucasggam...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 LucasGGamerM changed: What|Removed |Added OS|All |Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #72 from LucasGGamerM --- (In reply to LucasGGamerM from comment #71) > I have noticed something weird about this bug. After unplugging and plugging > my monitors back in, kwin only happens to leak memory (for me) when moving > the mouse on a monitor directly connected to the nvidia gpu, and it also > comes with momentary cpu usage spikes (to 20-30% usage from a normal 5%). I did some more testing, and it appears to happen movement happens on the monitors connected to the nvidia gpu, not just mouse movements. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #103 from LucasGGamerM --- In case anyone was wondering, 6.3.4 did not fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with NVIDIA GPUs driving multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #131 from LucasGGamerM --- (In reply to Evert Vorster from comment #130) > Spoke too soon again! > Having a new user account somewhat alleviated the issue, but it is still > there. > With an hour of usage after a screen power off and on, I can see the memory > usage creep up again. > kwin_wayland usually uses about 500MB of memory on my system, and it is now > nearing 1GB Try playing a video with a lot of movement in the external monitor, that usually makes the memory usage grow more noticeably -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502254] New: Window rules settings text inside dialogs are not visible.
https://bugs.kde.org/show_bug.cgi?id=502254 Bug ID: 502254 Summary: Window rules settings text inside dialogs are not visible. Classification: Plasma Product: plasmashell Version: 6.3.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lucasggam...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 179893 --> https://bugs.kde.org/attachment.cgi?id=179893&action=edit Opened windows class window with a dropdown menu open with empty text SUMMARY In the window rules options, every single spinner dialog (dropdown menus) has hidden text, making it not usable for configuration. STEPS TO REPRODUCE 1. Open window rules settings page 2. Create a new window rule 3. Click on the edit button of the window rule 4. Click on the window class dropdown menu (or any other dropdown menus present in this window) OBSERVED RESULT See that text inside the dropdown menu options is not visible. EXPECTED RESULT Text is visible. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with NVIDIA GPUs driving multi-monitor setups
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #135 from LucasGGamerM --- One interesting thing I just found out it's that the series of the nvidia driver which introduced explicit sync support on wayland was nvidia driver 555, and the latest known non memory leaking driver version is 550, that may be a hint that there is something going wrong with nvidia's and/or kwin's explicit sync implementation. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #144 from LucasGGamerM --- I have ran the instructions provided by TraceyC, and so far, with 3.8 gigs leaked, here is the "sudo perf report" output, I hope it is useful. ``` Samples: 886 of event 'cycles:P', Event count (approx.): 2804897302 Children Self Command Shared Object Symbol + 68,17% 0,00% kwin_waylandkwin_wayland[.] 0x5574b81d5495 ◆ + 68,17% 0,00% kwin_waylandlibc.so.6 [.] __libc_start_main@@GLIBC_2.34 ▒ + 68,17% 0,00% kwin_waylandlibc.so.6 [.] __libc_start_call_main ▒ + 68,17% 0,00% kwin_waylandkwin_wayland[.] 0x5574b81cefeb ▒ + 68,17% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] QCoreApplication::exec() ▒ + 68,17% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] QEventLoop::exec(QFlags) ▒ + 68,17% 0,00% kwin_waylandlibQt6Gui.so.6.9.0 [.] QUnixEventDispatcherQPA::processEvents(QFlags) ▒ + 67,58% 0,12% kwin_waylandlibQt6Core.so.6.9.0 [.] QEventDispatcherUNIX::processEvents(QFlags) ▒ + 56,26% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] QCoreApplication::notifyInternal2(QObject*, QEvent*) ▒ + 56,26% 0,00% kwin_waylandlibQt6Widgets.so.6.9.0 [.] QApplicationPrivate::notify_helper(QObject*, QEvent*) ▒ + 55,91% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] 0x7ff99ab6033a ▒ + 45,92% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] QTimerInfoList::activateTimers() ▒ + 45,46% 0,00% kwin_waylandlibQt6Core.so.6.9.0 [.] Q
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #155 from LucasGGamerM --- (In reply to Zamundaaa from comment #153) > As an update, we got a response from NVidia, they have a driver fix for this > in a future driver update. Was this discussion public? Can you share the link of this response? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities with different GPUs driving multi-monitor setups when a screen wakes / is added
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #147 from LucasGGamerM --- (In reply to TraceyC from comment #146) > (In reply to LucasGGamerM from comment #144) > > I have ran the instructions provided by TraceyC, and so far, with 3.8 gigs > > leaked, here is the "sudo perf report" output, I hope it is useful. > > Thank you for providing that. This report is set to high priority, so > hopefully one of the KWin developers can take a further look at this in the > near future. One thing of notice that my copy and paste did not include, and that I just noticed through putting both the normal kwin stack and the leaking kwin stack side by side in flamegraph was that the leaky kwin had a lot more "blocks" in their flamegraph graph. What I mean is that the stack in the leaky kwin is around 20-30 times bigger in terms of filesize when compared to a normal kwin stack, and it also looked like every function had made a bunch of instances of itself over and over again. I can share the graphs and the stack trace if requested, I tried sharing directly in a comment, but I think files are not allowed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 507450] New: Can't access root of network mounts.
https://bugs.kde.org/show_bug.cgi?id=507450 Bug ID: 507450 Summary: Can't access root of network mounts. Classification: Applications Product: dolphin Version First 25.04.3 Reported In: Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lucasggam...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Can't access the root (/) of any network mount through dolphin without it returning to the default location, in my case, the remote user's home STEPS TO REPRODUCE 1. Mount sftp share 2. Try to navigate to / OBSERVED RESULT See dolphin goes back to /home/remoteuser/ EXPECTED RESULT Have dolphin view / SOFTWARE/OS VERSIONS Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 32 GiB of RAM (29.2 GiB usable) Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3050 Laptop GPU ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
