Bug 465443 - kcalc eat cpu and going crazy
Summary: kcalc eat cpu and going crazy
Status: RESOLVED DUPLICATE of bug 453534
Alias: None
Product: kcalc
Classification: Applications
Component: general (show other bugs)
Version: 22.12.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-07 19:54 UTC by zvova7890
Modified: 2024-06-19 13:22 UTC (History)
1 user (show)

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


Attachments
CPU eat (168.61 KB, image/png)
2023-02-07 19:54 UTC, zvova7890
Details
Resize bug (179.81 KB, image/png)
2023-02-07 19:54 UTC, zvova7890
Details
Resize bug 2 (88.94 KB, image/png)
2023-02-07 19:55 UTC, zvova7890
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zvova7890 2023-02-07 19:54:32 UTC
Created attachment 156043 [details]
CPU eat

SUMMARY
kcalc in default window size blinking by "bit edit" field and eat 100% one core of CPU. I think it is somehow related to the scaling settings(150%). It is on x11 session. This version isn't first with this bug, at least 2-3 version ago I see that behavior. If resize window - kcalc is stop eat cpu and work fine until resize it to "default" window size.
Also, resizing of window is also behave not very well, see attachments.

STEPS TO REPRODUCE
1. Set 150% scale on X11
2. Open kcalc and setup as in picture(don't know if this matter)
3. Bit field is blinking and eat cpu

Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.9-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11700 @ 2.50GHz
Memory: 31.2 ГиБ of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Manufacturer: ASUS
Comment 1 zvova7890 2023-02-07 19:54:49 UTC
Created attachment 156044 [details]
Resize bug
Comment 2 zvova7890 2023-02-07 19:55:03 UTC
Created attachment 156045 [details]
Resize bug 2
Comment 3 popov895 2024-06-19 13:22:03 UTC

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