*** 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 STEPS TO REPRODUCE 1. Cloning Panels from one monitor to another 2. log onto process view in btop 3. gdb is running and memory usage continues to grow over time OBSERVED RESULT gdb just continues to run and adding more and more memory till it reaches capacity and i had to kill it EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora KDE KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION reported to fedora package maintainer and he said to send it upstream to KDE.
Nothing in Plasma launches gdb during normal usage. gdb *can* get launched if something on your system crashed, but that's normal behavior; it started running so it could debug the crash. If something crashed, please feel free to report that. Thanks!
(In reply to Nate Graham from comment #1) > Nothing in Plasma launches gdb during normal usage. > > gdb *can* get launched if something on your system crashed, but that's > normal behavior; it started running so it could debug the crash. > > If something crashed, please feel free to report that. Thanks! Plasma shell crashed, that triggered the gdb process on fedora. The gdb process kept allocating memory i eventually killed it over and over when the process was at 20gb oh memory. When i reported it to Fedora, they said it was a KDE issue and to post it here. Hence the bug report.
If something crashed, please report the crash itself. :) The fact that GDB went nuts trying to debug it is unfortunate, but not something under our direct control. It could be a sign that the crash resulted in infinite recursion, but it's impossible to know without being able to see a backtrace of the crash. If you can reproduce the crash, please do feel free to report that in a new bug report, with a symbolicated backtrace included. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to learn how to do that. Thanks!