Bug 510597 - Memory leak when using calculator with disabled numpad
Summary: Memory leak when using calculator with disabled numpad
Status: RESOLVED DUPLICATE of bug 509786
Alias: None
Product: krunner
Classification: Plasma
Component: calculator (other bugs)
Version First Reported In: 6.4.5
Platform: EndeavourOS Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-14 12:24 UTC by Paul Konecny
Modified: 2025-10-14 13:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Backtrace (hopefully) (36.09 KB, text/plain)
2025-10-14 12:24 UTC, Paul Konecny
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Konecny 2025-10-14 12:24:47 UTC
Created attachment 185763 [details]
Backtrace (hopefully)

SUMMARY
I tried to calculate 6*34 using krunner and I noticed it hung. I noticed it was using multiple gigabytes of RAM and I had to kill the process. I later noticed the numpad was disabled. 

STEPS TO REPRODUCE
1.   Open krunner using Alt+F2 
2.   Enter 6*34 with numpad disabled (so I basically entered  "cursor right * page down,cursor left")
2.5 I tried "cursor right * page down,cursor left" on the normal keyboard and it exhibits the same behaviour
3.   Possible memory leak occurs

OBSERVED RESULT
krunner hangs and its memory usages increases constantly. I usually kill it when it reaches 25 GB after a minute or so.

EXPECTED RESULT
No memory leak. When I enable the numpad the calculations are performed normally.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 128 GiB of RAM (125.7 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX


ADDITIONAL INFORMATION
gdb output attached (if that helps. Spoiler alert, I'm not a programmer).
Comment 1 Harald Sitter 2025-10-14 13:45:11 UTC

*** This bug has been marked as a duplicate of bug 509786 ***