Re: plasmashell cpu usage

Oleksandr Kryvulia <[email protected]>
Newsgroups gmane.comp.kde.freebsd
Message-ID <[email protected]>
Interestingly, the situation returns to normal after ~17 minutes of 
uptime. I checked this three times.

07.03.26 15:17, Oleksandr Kryvulia:
> After recent upgrade plasmashell and system clock process started 
> consuming a lot of cpu:
>
>  PID USERNAME    THR PRI NICE   SIZE    RES STATE    C   TIME    WCPU 
> COMMAND
>   11 root         12 199 ki31     0B   192K RUN      0  11:45 974,61% 
> idle
>    2 root         12 -50    -     0B   192K CPU0     0   0:46 100,40% 
> clock
> 62541 o.kryvulia   23  59    0  1439M   419M CPU3     3   0:42 100,02% 
> plasmashell
> 95957 o.kryvulia    5   0    0   428M   196M select  11   0:01   2,12% 
> konsole
> 67567 root          7   0    0   286M   146M select  10   0:01   0,29% 
> Xorg
>   12 root         53 -54    -     0B   848K WAIT     2   0:00   0,24% 
> intr
> 2317 root          1   0    0    15M  4220K CPU4     4   0:00   0,12% top
> 31319 o.kryvulia    1   0    0    15M  4548K select   5   0:00   0,06% 
> dbus-daemon
> 40246 o.kryvulia    9   0    0    65M    21M select   4   0:00   0,06% 
> xdg-desktop-portal
>
> Also I see a lot of interrupts genegated by cpu0:timer:
>
> # vmstat -i
> interrupt                          total       rate
> irq1: atkbd0                        1152          2
> irq9: acpi0                         1690          3
> irq12: psm0                           96          0
> irq27: ig4iic0                     12651         23
> irq56: iichid0                     12630         23
> cpu0:timer                     948004866    1735681
> cpu1:timer                         52907         97
> cpu2:timer                        250166        458
> cpu3:timer                        251124        460
> ....
>
> What could be causing this?
>
> FreeBSD 16.0-CURRENT #13 main-n284403-895a97c875a0
> plasma6-plasma-workspace-6.6.2
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.