| Summary: | Gentoo/Nvidia proprietary driver & plasmashell constantly growing in RAM usage until oom killer kicks in | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | unhappy-ending |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | fanzhuyifan, kde, nate |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
plasmashell-16gb
plasmashell-massif-graph plasmashell-massif-evaluations plasmashell-massif-allocators plasmashell-massif-output |
||
|
Description
unhappy-ending
2024-03-05 18:34:21 UTC
Created attachment 166436 [details]
plasmashell-16gb
I've compiled in X11 support and the xorg-server. Started up a fresh user with a new X11 session and the same issue is happening.
Including a screenshot of the wayland session using 18 gb of RAM.
I know Gentoo supports custom compile flags and such. Does this also happen with a "standard" compile of plasmashell? Also some sort of heap profile result of plasmashell would be extremely helpful https://stackoverflow.com/questions/4690800/how-to-profile-memory-usage https://stackoverflow.com/questions/700097/memory-allocation-profiling-in-c (In reply to fanzhuyifan from comment #2) > I know Gentoo supports custom compile flags and such. Does this also happen > with a "standard" compile of plasmashell? > > Also some sort of heap profile result of plasmashell would be extremely > helpful > > https://stackoverflow.com/questions/4690800/how-to-profile-memory-usage > https://stackoverflow.com/questions/700097/memory-allocation-profiling-in-c I was looking into Valgrind prior to making this post and will attempt it when I get some time. I am going to try an uncustomized USE flag setting for KDE and Qt, and see if there is any change, and then move on to looking into Valgrind. Created attachment 166453 [details]
plasmashell-massif-graph
Created attachment 166455 [details]
plasmashell-massif-evaluations
Created attachment 166456 [details]
plasmashell-massif-allocators
Created attachment 166457 [details]
plasmashell-massif-output
I started up a new session and ran valgrind --tool=massif --massif-out-file=/home/timothy/massif.out.plasma6 plasmashell --replace to collect some data for massif-visualizer. I included some screenshots of the data for a quick glance and the actual file to load up in massif-visualizer. Please let me know if there is anymore information you need, I will try my best to provide it. As of Plasma 6.0.2 and kernel version 6.8.1 I can't reproduce this anymore. I don't know if it had to do with a kernel config change, the new kernel itself, the update to wayland-protocols and egl-wayland supporting explicit sync or something else. (In reply to unhappy-ending from comment #9) > As of Plasma 6.0.2 and kernel version 6.8.1 I can't reproduce this anymore. > I don't know if it had to do with a kernel config change, the new kernel > itself, the update to wayland-protocols and egl-wayland supporting explicit > sync or something else. Thanks for all the info! Looking at the profiling data this might be an issue in nvidia driver version 550.54.14. Given that you can no-longer reproduce this in the latest version let's call this resolved-upstream for now. Hi, sorry to reopen this. I found out what triggers it. It's when slide show is enabled as the desktop background. As each image changes to the next, the memory usage goes up until it runs out and plasma crashes. I noticed it because I had set the image to change every 2 seconds (I was testing something else out) so it was easy to watch my memory widget go up every 2 seconds. Changing the background to something else like a plain color stops the memory from going up, but the memory also doesn't free itself. Wallpaper type Image is fine, but as I select a different image to decide which I want, the memory goes up for each one I click. I can keep doing this until I get an OOM and plasmashell crashes and restarts or OOM killer kicks in. I can even trigger this using Picture of the Day, and once each image is downloaded from each source, changing between the sources at random will increase the memory even when returning to an image that was once loaded. In addition to the info below, I also use a dual monitor setup with one scaled to 4k@150% and the other 1080p@75%. This current system is compiled with clang but also happened on a GCC compiled system which I was using when I first submitted the report. Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-clang (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 3950X 16-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2 Product Name: X570S PG Riptide Ok, that makes it the same as Bug 480693. Thank for following up. Since you seem very technically capable, it would be amazing if you wanted to investigate the issue further and look into fixing it! *** This bug has been marked as a duplicate of bug 480693 *** |