[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Kirill changed: What|Removed |Added CC||kyrylo.shaki...@gmail.com --- Comment #14 from Kirill --- I have it reproducible for a long time. Also, when, just after KCalc starts, I hover mouse pointer on drop-down menu on top, it became stroboscopic - quickly light up and light down like disco. And yes, I use 150% scaling in display settings if this is somehow related. kcalc 23.08.3-1 Operating System: Manjaro Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 62.1 GB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: Victus by HP Laptop 16-e0xxx -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 --- Comment #13 from David Warner --- I'm not seeing this on a fresh Fedora 38 install with KCalc 23.04.0 (Plasma 5.27.4, KDE Frameworks 5.105.0, Qt 5.15.9, X11), though I'm sure it was still happening on my previous Fedora 37 install with the same versions. I'm confused, but happy if it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Diego changed: What|Removed |Added CC||diego...@zoho.com --- Comment #12 from Diego --- To me the issue is most evident when you open the bit edit view: "Settings → Show bit edit". May be related to: https://bugs.kde.org/show_bug.cgi?id=453775 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 --- Comment #11 from dmbt...@gmail.com --- Just a thought... Could this have to do with hidpi scaling? On Wed, Oct 19, 2022, 1:49 PM P. Förster wrote: > https://bugs.kde.org/show_bug.cgi?id=453534 > > P. Förster changed: > >What|Removed |Added > > > CC||kde.p-foers...@gmx.de > > --- Comment #10 from P. Förster --- > Just wanted to add that I can still confirm this with KCalc version > 22.08.2. > > The menu is flickering for me, too. Also, resizing fixes the problem for > me. > > -- System information -- > Operating System: EndeavourOS > KDE Plasma Version: 5.26.1 > KDE Frameworks Version: 5.99.0 > Qt Version: 5.15.6 > Kernel Version: 6.0.2-arch1-1 (64-bit) > Graphics Platform: X11 > Processors: 12 × Intel® Core™ i7-10710U CPU @ 1.10GHz > Memory: 15,3 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics > Manufacturer: Intel(R) Client Systems > Product Name: NUC10i7FNK > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 P. Förster changed: What|Removed |Added CC||kde.p-foers...@gmx.de --- Comment #10 from P. Förster --- Just wanted to add that I can still confirm this with KCalc version 22.08.2. The menu is flickering for me, too. Also, resizing fixes the problem for me. -- System information -- Operating System: EndeavourOS KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10710U CPU @ 1.10GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Intel(R) Client Systems Product Name: NUC10i7FNK -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 kde-bugtrac...@caspertech.co.uk changed: What|Removed |Added CC||kde-bugtracker@caspertech.c ||o.uk --- Comment #9 from kde-bugtrac...@caspertech.co.uk --- Just to note that I see this also on Gentoo with kcalc-22.04.3 I have 2 x 4k monitors with 150% global scale - given the previous comments, maybe this is relevant -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 david.p.war...@gmail.com changed: What|Removed |Added Version|22.04.0 |22.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 Ryan Ronnander changed: What|Removed |Added CC||rronnan...@gmail.com --- Comment #8 from Ryan Ronnander --- (In reply to roger.koot from comment #5) > If you resize the kcalc window, the cpu usage drops to expected values. Wow, this actually works, but upon closing and reopening kcalc, the behavior resumes until resized. I cannot reproduce this on other KDE systems. The menu rapidly flickers when this bug occurs, as if some redraw event is constantly being executed until the window is resized. I believe I've tried this on both X11 and Wayland, both hit 100% CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 --- Comment #7 from roger.k...@gmail.com --- (In reply to dmbtech from comment #6) > (In reply to roger.koot from comment #5) > > If you resize the kcalc window, the cpu usage drops to expected values. > > Wow, totally right. Resizing drops cpu to normal levels. Any idea why? Regrettably not. It was just a hunch. Could well be something X11 related but I haven't tested this under Wayland though. I don't even know whether the kcalc-100% bug is triggered on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 --- Comment #6 from dmbt...@gmail.com --- (In reply to roger.koot from comment #5) > If you resize the kcalc window, the cpu usage drops to expected values. Wow, totally right. Resizing drops cpu to normal levels. Any idea why? -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 roger.k...@gmail.com changed: What|Removed |Added CC||roger.k...@gmail.com --- Comment #5 from roger.k...@gmail.com --- If you resize the kcalc window, the cpu usage drops to expected values. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 stefan...@posteo.de changed: What|Removed |Added CC||stefan...@posteo.de --- Comment #4 from stefan...@posteo.de --- I can confirm this. My system: Operating System: openSUSE Tumbleweed 20220617 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.18.4-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 afedotov...@outlook.com changed: What|Removed |Added CC||afedotov...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534
--- Comment #3 from dmbt...@gmail.com ---
Couldn't figure out how to edit original comment. But also wanted mention, the
cpu usage does not appear to occur with regular user, and strace I notice a
loop of repeats when idle(not sure if this is useful):
...
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\24\0\6\0\6\0`\10\263\1\0\0\6\0\0\0\0\0\0\0\4\0\0\0",
iov_len=24}], 1) = 24
futex(0x7ffcc6377e48, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\30\0\6\0`\10(\0\0\0)\0\0\0
\0\0\0\22\0\0\0R\3\0\0\0\0\0\0"..., iov_len=116}], 1) = 116
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\0\1\0", iov_len=4}], 1) = 4
futex(0x7ffcc6377b48, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base=";\3\5\0\17\0`\10\0\0\0\0\0\0\0\0\211\1\302\1\202\3\n\0\6\0`\10\17\0`\10"...,
iov_len=76}], 1) = 76
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\v\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\24\0\6\0\6\0`\10\263\1\0\0\6\0\0\0\0\0\0\0\4\0\0\0",
iov_len=24}], 1) = 24
futex(0x7ffcc6377e48, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = 0
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\30\0\6\0`\10(\0\0\0)\0\0\0
\0\0\0\22\0\0\0R\3\0\0\0\0\0\0"..., iov_len=116}], 1) = 116
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\0\1\0", iov_len=4}], 1) = 4
futex(0x7ffcc6377b48, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base=";\3\5\0\17\0`\10\0\0\0\0\0\0\0\0\211\1\302\1\202\3\n\0\6\0`\10\17\0`\10"...,
iov_len=76}], 1) = 76
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\v\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\24\0\6\0\6\0`\10\263\1\0\0\6\0\0\0\0\0\0\0\4\0\0\0",
iov_len=24}], 1) = 24
futex(0x7ffcc6377e48, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\30\0\6\0`\10(\0\0\0)\0\0\0
\0\0\0\22\0\0\0R\3\0\0\0\0\0\0"..., iov_len=116}], 1) = 116
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="+\0\1\0", iov_len=4}], 1) = 4
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x5571f29d45d8, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3,
[{iov_base=";\3\5\0\17\0`\10\0\0\0\0\0\0\0\0\211\1\302\1\202\3\n\0\6\0`\10\17\0`\10"...,
iov_len=76}], 1) = 76
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, 0) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\v\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5,
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 dmbt...@gmail.com changed: What|Removed |Added CC||dmbt...@gmail.com --- Comment #2 from dmbt...@gmail.com --- I can confirm I am seeing this also with 22.04.1, but with Arch Linux, KDE Frameworks Version 5.94.0 , QT Version 5.15.4 (built against 5.15.3), 5.17.6-arch1-1. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 david.p.war...@gmail.com changed: What|Removed |Added CC||david.p.war...@gmail.com --- Comment #1 from david.p.war...@gmail.com --- I'm seeing this with 22.04.1 (environment: Fedora 36, KDE Plasma 5.24.5, KDE Frameworks 5.93.0, Qt 5.15.3, Kernel 5.17.6, X11). -- You are receiving this mail because: You are watching all bug changes.
