| Summary: | gdb memory leak | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | grumpydonut |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | kdedev, nate, niccolo.venerandi, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
grumpydonut
2025-11-23 17:02:19 UTC
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! |