Expanding on Shambler's 2019/03/23 comment, clock_gettime showing up in
the strace can be caused by the TSC clock source being marked unstable
(after a sleep for some people, like me).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
This bug is closed because:
(a) The original reporter can't reproduce it any more; and
(b) The developer can't reproduce it any more.
If there are any remaining issues then please open a new bug by running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a memb
I see same behaviour. recvmsg() with EAGAIN failures (lot!!). CPU
utilization is not very high for me. Like around 3% but constant usage.
I could see difference in battery life. Switched back to unity for now.
I see the status as "Fix released". Which ubuntu version has the fix?
Or is it possible
See this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1821441
It looks like (at least for some people) there was a wider root cause -
confirmed by the trace in comments above, where expensive clock_gettime
calls are observed.
--
You received this bug notification because
Pedro,
That's enough for me, thanks.
This bug is now closed. If anyone experiences any more issues at all
then please open a new bug by running:
ubuntu-bug gnome-shell
And if anyone did want to test 19.04 then you can find it here:
http://cdimages.ubuntu.com/daily-live/current/
But if you
Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried:
- Booting 18.04.2 from a usb disk
- The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of
other bugs)
- The 18.04 default Ubuntu Xorg session
all of them seem to be showing reasonable <1% gnome-shell CPU usage whe
Pedro, please answer comment #18. I would like to know if 18.10 or 19.04
has changed the situation for you.
---
Nicolas, this bug is not about showing seconds in the clock. Please
comment in bug 1814125 instead for that issue and not here. Or log a new
bug.
---
Mark, this bug is about the CPU u
I really hope this is fixed by 19.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1773959
Title:
High CPU usage by gnome-shell when only running gnome-terminal
To manage not
I disabled all extensions in Firefox. I'm trying to fix my high CPU. I'm
not a computer adept.
mark@Lexington:~$ ps aux | grep 'Z'
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 2587 0.0 0.0 0 0 ?Z08:05 0:00 [apccontrol]
mark 2608
After years of high CPU usage with gnome-shell and not finding the
issue, I finally found this bug report, disable showing the seconds of
the clock in the top panel and now the CPU usage is between 0-1% instead
of 40% and more. What the heck? Thank you!
Still clock_gettime is active 71% of the tim
Actually... my gnome-shell seems to spend about 25% of its time in the
kernel ("system time"), and 75% in user space. That means 0.25*0.8327
--> around 20% of gnome-shell's time is spent inside the clock_gettime
system call. This is quite significant actually. Thanks.
--
You received this bug not
Regarding:
% time seconds usecs/call calls errors syscall
-- --- --- - -
83.37 2.716542 2 1494072 clock_gettime
I believe that's 83.37% of the process' system time. It's not the
overall CPU usage of the function. If you use the 'time' command
In case the video is still suspected:
pat@wopr:~$ xrandr
Screen 0: minimum 8 x 8, current 9600 x 2160, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right
I see 9% consistently, and as with those above, clock_gettime seems to
be the culprit:
pat@wopr:~$ sudo strace -c -p 29333
[sudo] password for pat:
strace: Process 29333 attached
^Cstrace: Process 29333 detached
% time seconds usecs/call callserrors syscall
-- --- --
Yes this bug is about buffer copies really, and so the performance of
software-rendered toolkits like GTK.
Please be careful to not discuss moving the mouse in this bug because
that's a different problem. Please open a new bug for mouse movements
and mention https://gitlab.gnome.org/GNOME/mutter/i
I've noticed the same issue with all extensions disabled. It seems very
correlated with changes on the screen, to include moving the mouse. I've
watched 'top' over an SSH connection to the system running gnome. If I
have just a terminal window open any updates in that window cause gnome-
shell CPU
Moving the mouse around is
https://gitlab.gnome.org/GNOME/mutter/issues/283, not this one. Feel
free to open a new Launchpad bug for it.
This bug is about when only gnome-terminal is running without any
interaction. Not moving the mouse.
--
You received this bug notification because you are a me
Tried on both 18.04 (gnome-shell version 3.28.3 and 3.28.1) and 18.10 (3.30.1).
No extensions at all.
Got cpu usage changing from 20% to 90% just moving mouse around.
3.28.1 behaviour is slightly better: from 15% to 30-40%
--
You received this bug notification because you are a member of Ubunt
Pedro,
I can't seem to find any significant CPU usage by gnome-shell when the
terminal is busy, using Ubuntu 18.10.
Can you please try live booting 18.10 and tell us if you find that is better
now?
http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso
** Changed in: gnome-shell (Ubunt
Also,
Everyone please REMOVE or DISABLE all your extensions before measuring
the CPU usage of gnome-shell. We are not interested in the performance
problems introduced by extensions here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
Gustuv:
Please open a new bug for the issue you describe, by running:
ubuntu-bug gnome-shell
If gnome-shell is idling with that much CPU usage then it's usually an
extension to blame.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
gnome-shell idling at around 17% usage right now, here's an strace for
around 15 seconds:
strace: Process 963 attached
^Cstrace: Process 963 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
28,650,167283
Same problem here, running Ubuntu 18.04 on a Dell XP 9570 with a screen
resolution of 3840x2160.
I am also seeing a lot of errors in recvmsg:
strace: Process 1312 attached
^Cstrace: Process 1312 detached
% time seconds usecs/call callserrors syscall
-- --- --- ---
Thanks for reminding me about this bug. It's now on this checklist:
https://trello.com/c/pe5mRmx7
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1773959
Title:
High CPU usage
10 seconds of strace on core i5
strace -c -p 17477
strace: Process 17477 attached
^Cstrace: Process 17477 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
64.240.445795 2258405 clock
I'm finding the same symptoms from gnome-shell, relatively high cpu use by
gnome-shell with all extenstions deisabled (if I turn on extensions the cpu
usages is ridiculous high, in the range of 20-50%).
I checked strace as above and am finding the same high number of errors from
the recvmsg cal
I'm seeing moderately high CPU usage from the gnome-shell process as
well. It seems to stay running at at least 5% at all times. I decided to
use strace to see what it was doing:
$ sudo strace -c -p 6916
strace: Process 6916 attached
strace: Process 6916 detached
% time seconds usecs/call
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1773959
Title:
High CPU usage by gnome-shell when only run
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1773959
Title:
High CPU usage by gnome-shell when only runni
Did a clean install and here are the numbers with a Xorg session:
- all default: less than 1% (comparable or even better to compiz)
- turning on seconds on the top bar clock: around 3%
- turning on extensions (particularly system monitor): 6-9%
So it seems gnome-shell is perfectly capable of usin
Just tested this on Wayland and the situation seems slightly better. The
same test (just the terminal, no extensions) is about 2-3% of CPU usage
(compares with less than 1% for compiz) and when I turn on extensions
(particularly system monitor) it goes to 5-7%. Not great but better.
Great work on
Yeah, I know. I'm building a list of issues here:
https://trello.com/c/pe5mRmx7
Do you find the problem is better in Gnome Shell on Xorg, compared to
Gnome Shell on Wayland?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you ar
For reference, logging in with Unity on the same hardware compiz uses
about 1% or less CPU. So gnome-shell seems to be using 10x the CPU on
this hardware at least. This was an upgraded install from 16.04 and I'll
be trying a clean reinstall instead.
--
You received this bug notification because y
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1773959
Title:
High CPU usage by gnome-shell when only runni
The resolution is 2560x1440. I was testing with the terminal window
maximized but the outcome is the same when the terminal is just a small
window in the middle. The CPU usage is roughly half when the computer is
charging, probably because the CPU is throttled up.
--
You received this bug notific
36 matches
Mail list logo
