Summary: | std::bad_alloc: integer overflow in screenGeometry() via qdbus plasma scripting freezes plasmashell at 100% CPU usage indefinitely | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Benjamin Flesch <benjaminflesch> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | aacid, kde, nate, security |
Priority: | NOR | Keywords: | efficiency-and-performance |
Version First Reported In: | 5.27.10 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/5efaf8564183a01483f072265f4c0e7f2d927f68 | Version Fixed In: | 6.5.0 |
Sentry Crash Report: |
Description
Benjamin Flesch
2024-01-18 18:37:18 UTC
I can't reproduce a crash, but instead plasmashell takes up 100% of a CPU core, hangs, and the following error is printed to the log: Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. This is somewhat worse than a crash since plasmashell won't auto-recover; you have to know technical recovery tools (I had to `killall -9 plasmashell`) or restart the computer. Raising the severity. Is there a particular reason that evaluateScript does not have a timer watchdog like we have in Okular so that JS can only execute for X amount of time? A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5806 Git commit 5efaf8564183a01483f072265f4c0e7f2d927f68 by Albert Astals Cid. Committed on 07/09/2025 at 14:01. Pushed by aacid into branch 'master'. Limit evaluateScript execution at 2 seconds M +20 -0 shell/scripting/scriptengine.cpp M +3 -0 shell/scripting/scriptengine.h https://invent.kde.org/plasma/plasma-workspace/-/commit/5efaf8564183a01483f072265f4c0e7f2d927f68 |