[plasmashell] [Bug 465990] New: Plasmashell eats more than 10Go of RAM
https://bugs.kde.org/show_bug.cgi?id=465990 Bug ID: 465990 Summary: Plasmashell eats more than 10Go of RAM Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: quelque_...@yahoo.fr Target Milestone: 1.0 Created attachment 156422 --> https://bugs.kde.org/attachment.cgi?id=156422&action=edit Ram usage as shown by top. SUMMARY At the moment, I have my plasmashell process using more than 10Go of RAM, plus the start menu opens but refuse to launch any program. The alt+f2 command works though. Some extra details that may be useful: After an unexpected shutdown during an update, I had to fix the system, and reinstalled a couple of programs, including linux that was broken. At reboot, I had this issue with plasmashell so I tried several things: - reinstall every program that started with plasma-* - remove the plasma* files in ~/.cache - delete ~/.config/plasma-workspace Nothing helped. STEPS TO REPRODUCE 1. Start the computer 2. Login in SDDM 3. Open the Konsole (with alt+f2) and execute `top`. OBSERVED RESULT The `top` command shows that plasmashell has more than 10Go of RAM used, even at startup (and it stays that high during the usage of plasmashell). Plus, I can't start any application from the start menu (even though the start menu open as expected). The rest of plasmashell seems to work as expected. EXPECTED RESULT I expect the RAM consumption to be under 500Mo, like before the upgrade/crash. And to be able to start applications from the start menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 6.1.12-arch1-1 (64-bit) KDE Plasma Version: 5.27.0-1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Using X11 ADDITIONAL INFORMATION I will try to provide as much relevant information that I can, don't hesitate to ask for more. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465990] Plasmashell eats more than 10Go of RAM
https://bugs.kde.org/show_bug.cgi?id=465990 --- Comment #1 from dmidge --- Created attachment 156423 --> https://bugs.kde.org/attachment.cgi?id=156423&action=edit Stacktrace (if usefull) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465990] Plasmashell eats more than 10Go of RAM
https://bugs.kde.org/show_bug.cgi?id=465990 --- Comment #2 from dmidge --- Created attachment 156424 --> https://bugs.kde.org/attachment.cgi?id=156424&action=edit journalctl output related to plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465990] Plasmashell eats more than 10Go of RAM
https://bugs.kde.org/show_bug.cgi?id=465990 --- Comment #3 from dmidge --- For some reason, removing all the .config/plasm* did the trick for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456977] New: FATAL ERROR: KWin could not find the KWinX11Platform plugin
https://bugs.kde.org/show_bug.cgi?id=456977 Bug ID: 456977 Summary: FATAL ERROR: KWin could not find the KWinX11Platform plugin Product: kwin Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: quelque_...@yahoo.fr Target Milestone: --- SUMMARY During the start of a x11 session, kwin cannot start the plasma session. STEPS TO REPRODUCE 1. log-in in sddm 2. Wait until it works. But it stays forever, without having the kernel to freeze. OBSERVED RESULT The gear of the login screen spins and it doesn't arrive to the plasma screen. The kernel is still responsive: you can kill X11 and start again, with the same result. The ssh is fine. The mouse appears and can move. Just KDE is not usable (no alt+f1 nor alt+f2), no display (it is black with the gear still on). Clearing the kde config files didn't help. The end of .xsession-errors gives: kdeinit5: opened connection to :0 org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0 kf.coreaddons: "Could not load plugin from notificationhelper: The shared library was not found." kf.coreaddons: "Could not find plugin kded_notificationhelper" kf.kded: Could not load kded module "notificationhelper":"Could not find plugin kded_notificationhelper" (library path was:"notificationhelper") Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing. FATAL ERROR: KWin could not find the KWinX11Platform plugin EXPECTED RESULT Plasmashell to appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 22.04. KDE Plasma Version: 5.24.4 Using the proprietary nvidia drivers. Result of the kwin-x11 version: Package: kwin-x11 Version: 4:5.24.4-0ubuntu1 Priority: optional Section: universe/kde Source: kwin Origin: Ubuntu Maintainer: Kubuntu Developers Original-Maintainer: Debian Qt/KDE Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1 451 kB Provides: kwin, x-window-manager Depends: kwin-common (= 4:5.24.4-0ubuntu1), libc6 (>= 2.34), libepoxy0 (>= 1.0), libgcc-s1 (>= 3.4), libkf5configcore5 (>= 5.90.0~), libkf5configgui5 (>= 5.90.0~), libkf5configwidgets5 (>= 5.90.0~), libkf5coreaddons5 (>= 5.90.0~), libkf5crash5 (>= 5.90.0~), libkf5globalaccel-bin, libkf5globalaccel5 (>= 5.90.0~), libkf5i18n5 (>= 5.90.0~), libkf5notifications5 (>= 5.90.0~), libkf5plasma5 (>= 5.90.0~), libkf5quickaddons5 (>= 5.26.0), libkf5service-bin, libkf5service5 (>= 5.90.0~), libkf5windowsystem5 (>= 5.90.0~), libkwaylandserver5 (>= 5.24.4), libkwaylandserver5-5.24, libkwineffects13 (= 4:5.24.4-0ubuntu1), libkwinglutils13 (= 4:5.24.4-0ubuntu1), libkwinxrenderutils13 (= 4:5.24.4-0ubuntu1), libqaccessibilityclient-qt5-0 (>= 0+git20130108), libqt5core5a (>= 5.15.1), libqt5dbus5 (>= 5.15.0~), libqt5gui5 (>= 5.15.0~) | libqt5gui5-gles (>= 5.15.0~), libqt5qml5 (>= 5.15.0~), libqt5quick5 (>= 5.15.0~) | libqt5quick5-gles (>= 5.15.0~), libqt5widgets5 (>= 5.15.0~), libqt5x11extras5 (>= 5.15.0~), libstdc++6 (>= 11), libx11-6, libxcb-composite0, libxcb-keysyms1 (>= 0.4.0), libxcb-randr0 (>= 1.3), libxcb-render0, libxcb-shape0, libxcb-xfixes0, libxcb1 (>= 1.6), libxi6 (>= 2:1.5.99.2) Breaks: kwin-common (<< 4:5.20.4-4~) Replaces: kwin-common (<< 4:5.20.4-4~) Homepage: https://projects.kde.org/projects/kde/workspace/kwin Task: kubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop Download-Size: 417 kB APT-Manual-Installed: yes APT-Sources: http://fr.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Description: KDE window manager, X11 version KWin (pronounced as one syllable "kwin") is the window manager for the KDE Plasma Desktop. It gives you complete control over your windows, making sure they're not in the way but aid you in your task. It paints the window decoration, the bar on top of every window with (configurable) buttons like close, maximize and minimize. It also handles placing of windows and switching between them. . This package is part of the KDE base workspace module. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436542] Plasmashell hangs in libfolderplugin.so when a highdpi monitor is pluged in
https://bugs.kde.org/show_bug.cgi?id=436542 dmidge changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436542] New: Plasmashell hangs when a highdpi monitor is pluged in.
https://bugs.kde.org/show_bug.cgi?id=436542 Bug ID: 436542 Summary: Plasmashell hangs when a highdpi monitor is pluged in. Product: plasmashell Version: 5.21.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: quelque_...@yahoo.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 138118 --> https://bugs.kde.org/attachment.cgi?id=138118&action=edit Stacktrace with gdb SUMMARY The system hangs when the highDPI monitor is plugged in. STEPS TO REPRODUCE 1. Plugin the HighDPI monitor to the HDMI of the laptop. OBSERVED RESULT The system hangs. No control over audio anymore. It is not possible to have any control, even on the resolution or luminosity anymore. The only way to fix the hang is to kill plasmashell, unplug the monitor and restart plasmashell. EXPECTED RESULT Well, having another monitor working. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux with plasma 5.24.1-1 but also previous versions. (available in About System) Qt Version: 5.15.2 ADDITIONAL INFORMATION Plasma is running with Xorg. The video card is: `$lspci -v 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 1108 Flags: bus master, fast devsel, latency 0, IRQ 48, IOMMU group 0 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at d280 (64-bit, prefetchable) [size=8M] I/O ports at 5000 [size=256] Memory at d350 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: amdgpu Kernel modules: amdgpu ` Added, a couple of stacktraces when it occurs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436542] Plasmashell hangs in libfolderplugin.so when a highdpi monitor is pluged in
https://bugs.kde.org/show_bug.cgi?id=436542 --- Comment #2 from dmidge --- Created attachment 138295 --> https://bugs.kde.org/attachment.cgi?id=138295&action=edit Asked backtrace with dbg infos Addition of the asked backtrace containing the debug informations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436542] Plasmashell hangs in libfolderplugin.so when a highdpi monitor is pluged in
https://bugs.kde.org/show_bug.cgi?id=436542 dmidge changed: What|Removed |Added Resolution|BACKTRACE |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #3 from dmidge --- The backtrace is in the second file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436542] Plasmashell hangs in libfolderplugin.so when a highdpi monitor is pluged in
https://bugs.kde.org/show_bug.cgi?id=436542 --- Comment #4 from dmidge --- Hi again, Could you confirm that there is no missing information? Please don't hesitate to ask further information if needed. Thanks! Cheers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456977] FATAL ERROR: KWin could not find the KWinX11Platform plugin
https://bugs.kde.org/show_bug.cgi?id=456977 dmidge changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #4 from dmidge --- I did reproduce the same problem. The file /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so does exist: $ ls -l /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so -rw-r--r-- 1 root root 317816 août 16 10:06 /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412892] New: plasmashell hangs and eat 100% of CPU, probably related to screen management.
https://bugs.kde.org/show_bug.cgi?id=412892 Bug ID: 412892 Summary: plasmashell hangs and eat 100% of CPU, probably related to screen management. Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: quelque_...@yahoo.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123169 --> https://bugs.kde.org/attachment.cgi?id=123169&action=edit gdb trace of when it hangs. SUMMARY Hanging of plasmashell. It seems related to an external monitor on a laptop. STEPS TO REPRODUCE 1. restart the computer, with two screen 2. Wait and see plasmashell eating 100% of the CPU while not showing up. EXPECTED RESULT Some plasmashell features, such as the taskbar, should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.16.5-1 The gdb trace is attached to this ticket. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412912] New: Dolphin hangs.
https://bugs.kde.org/show_bug.cgi?id=412912 Bug ID: 412912 Summary: Dolphin hangs. Product: dolphin Version: 19.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: quelque_...@yahoo.fr CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123171 --> https://bugs.kde.org/attachment.cgi?id=123171&action=edit Gdb trace of dolphin when it hangs. SUMMARY While moving a file or creating a folder, dolphin hangs. I don't know if that matters, but plasmashell was not running at that time. (Cause: plasmashell bug reported - 412892) STEPS TO REPRODUCE 1. right click in a folder 2. new > folder 3. Wait. OBSERVED RESULT It just hangs there until KDE consider that the application crashed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.5-1 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412892] plasmashell hangs and eat 100% of CPU, probably related to screen management.
https://bugs.kde.org/show_bug.cgi?id=412892 --- Comment #1 from dmidge --- Would that be possible to change this bug report importance to "crash". I don't seem to have access to that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412912] Dolphin hangs.
https://bugs.kde.org/show_bug.cgi?id=412912 --- Comment #2 from dmidge --- I am not sure. I didn't reproduce it since I rebooted. I think that was more a temporary bug, because my computer went in some bad local state. I guess? Anyway, that probably highlight a more deeply rooted problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412892] plasmashell hangs and eat 100% of CPU, probably related to screen management.
https://bugs.kde.org/show_bug.cgi?id=412892 dmidge changed: What|Removed |Added Ever confirmed|0 |1 Resolution|BACKTRACE |--- Status|NEEDSINFO |REOPENED --- Comment #3 from dmidge --- I am not sure to understand what do you mean. I was using the repository packages. The trace were provided by running "gdb plasmashell" then a series of "continues" with "thread apply all backtrace". So it helps to know where it hangs/stalls. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390694] New: Crash during my application research in the alt+f1 menu
https://bugs.kde.org/show_bug.cgi?id=390694 Bug ID: 390694 Summary: Crash during my application research in the alt+f1 menu Product: plasmashell Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: quelque_...@yahoo.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.1) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I was just looking fot the Kalc application, that I mistyped in calc. The result found where not satisfactory so I pressed the back button, and it crashed... The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81e11e8800 (LWP 605))] Thread 26 (Thread 0x7f80b57f5700 (LWP 2064)): #0 0x7f81d9ed83bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f81dad2c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f80ed37142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f80ed376479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f80ed3764d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f80ed373c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f81dad2ab4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f81d9ed208c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f81da630e7f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f80b5ff6700 (LWP 2063)): #0 0x7f81d9ed83bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f81dad2c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f80ed37142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f80ed376479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f80ed3764d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f80ed373c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f81dad2ab4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f81d9ed208c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f81da630e7f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f80b67f7700 (LWP 2062)): #0 0x7f81d9ed83bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f81dad2c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f80ed37142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f80ed376479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f80ed3764d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f80ed373c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f81dad2ab4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f81d9ed208c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f81da630e7f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f80b6ff8700 (LWP 2061)): #0 0x7f81d9ed83bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f81dad2c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f80ed37142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f80ed376479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f80ed370924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f80
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 dmidge changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #14 from dmidge --- Hi again, I am re-opening this ticket because I have some new information to provide. I used to have a widget that displayed every second or so, the use of the CPU, the RAM&swap and the network. Thus, I guess it made a lot of refresh. Removing that on the tray bar, I still have my CPU usage growing to 100% with plasmashell, but it is growing slowly. I can work with my computer for more than one hour without killing plasmashell just because I removed this widget. Before that, I needed to kill plasmashell under 5 minutes. So I guess there is something going on with the widget that refreshes a lot the display of the tray bar and the increasing CPU usage of plasmashell. (Because now, the CPU usage of plasmashell grows linearly over time, until I kill it and restart it. It was probably the case before but I didn't have time to notice it.) Funny thing is: it used not to happen to me with the plasmashell and nouveau version that were 1 year old. Now, my plasma-workspace version is 5.10.5-4 and xf86-video-nouveau is 1.0.15-2. Please ask me if you need further information. :o) Cheers! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] New: Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 Bug ID: 381608 Summary: Plasmashell use 100% cpu Product: plasmashell Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: quelque_...@yahoo.fr CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 For some reason, plasmashell uses more than 100% cpu, I don't why. I think it is when I leave my computer stalling for more than 5min, but I don't need to get to the screensaver to have that. I'm using plasmashell 5.10.2, on archlinux, with the nouveau driver 1.0.15-1. uname -a: Linux coincoin.mooo.com 4.11.5-1-ARCH #1 SMP PREEMPT Wed Jun 14 16:19:27 CEST 2017 x86_64 GNU/Linux Nothing's relevant in dmesg. Here's the stack trace: Thread 10 (Thread 0x7fff0d27e700 (LWP 16065)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fff0e903427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fff3747f700 (LWP 16053)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x75947836 in () at /usr/lib/libQt5Quick.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fff3cd0f700 (LWP 16052)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffc56a52fb in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #2 0x7fffc56a5037 in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fffc7dea700 (LWP 16051)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x77662ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x77662b09 in () at /usr/lib/libQt5Script.so.5 #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fffd1b0b700 (LWP 16050)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fffd3bb3700 (LWP 16049)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x74d8f645 in () at /usr/lib/libQt5Qml.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fffda319700 (LWP 16048)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(Q
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #1 from dmidge --- Please ask if you need more info. Thanks for your job! :o) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #2 from dmidge --- another stacktrace a while later: thread apply all bt full Thread 13 (Thread 0x7ffef7082700 (LWP 17326)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffe5ee5ee1 in () at /usr/lib/libpulse.so.0 #2 0x7fffe5ed76f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fffe5ed7d8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fffe5ed7e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fffe5ee5e29 in () at /usr/lib/libpulse.so.0 #6 0x7fffe5875fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7ffef870b700 (LWP 17325)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x74d8f645 in () at /usr/lib/libQt5Qml.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fff0d57e700 (LWP 17300)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fff0ec03427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fff3747f700 (LWP 17289)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 ---Type to continue, or q to quit--- #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x75947836 in () at /usr/lib/libQt5Quick.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fff3cd0f700 (LWP 17287)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffc56a52fb in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #2 0x7fffc56a5037 in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fffc7dea700 (LWP 17285)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x77662ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x77662b09 in () at /usr/lib/libQt5Script.so.5 #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fffd1b0b700 (LWP 17284)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fffd3bb3700 (LWP 17283)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 ---Type to continue, or q to quit--- #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #4 from dmidge --- (In reply to Boian Berberov from comment #3) > dmidge, do you have any FolderView widgets on your desktop? Hi Boian, Yes, I do. I have two folders. Are they the culprits? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #7 from dmidge --- Well, it may or may not be related to what Boian said, but I have a lot of identical messages: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:282:17: QML Text: Binding loop detected for property "width" Maybe it is one of the cause of the loop? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 dmidge changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #9 from dmidge --- Well, I don't think it is related to the folder view. In the meantime, I can't resize the folder view anymore :'( I reopen this ticket with a bigger stacktrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #10 from dmidge --- Created attachment 106496 --> https://bugs.kde.org/attachment.cgi?id=106496&action=edit Several stacktraces of plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #11 from dmidge --- Btw, when I say the plasmashell takes 100%cpu, it is always above that. I guess one thread is taking 100%, the others take the normal amount, like around 10% fluctuating over time... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #13 from dmidge --- Ok, I understand. However, I am willing to give a try. But I got to tell you: I've never done that before, and I may need some step by step instruction. I guess I should install qt5-base? -- You are receiving this mail because: You are watching all bug changes.
