I think what reported by Lorens may be totally unrelated to the use of
Chrome. The use of VirtualBox, latest version 5.2.18, with a Ubuntu
18.04 64bit guest with 3D acceleration **enabled** and maximum VRAM
configured (128MB) is completely unusable because of extremely high
memory usage of
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Lorens,
You may be experiencing multiple bugs. We would like each bug report to
be about a single issue, but here's a list of some of the major issues
we hope to fix soon:
https://trello.com/c/pe5mRmx7
The list is likely to grow a little too.
--
You received this bug notification because
I am not quite sure I have *this* bug, because it continues after I
close Chrome.
I am using Bionic Beaver in a VirtualBox with 4 CPU threads and 4096
(later 6144) MB RAM out of my 2015 MacBook Pro's 8 CPU threads and 16 GB
RAM. When I start up, everything seems fine. With one single Terminal
All,
Can you please test to see if moving the Chrome window away from the
launcher (on the left) reduces the CPU usage of gnome-shell?
I know that having windows changing near the launcher is a problem. And
I will get back to fixing that soon (bug 1743976).
** Changed in: gnome-shell (Ubuntu)
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.
** Summary changed:
- gnome-shell + chrome doing nothing consumes 60%+ CPU all the time
+ gnome-shell + chrome doing nothing consumes high CPU all the time
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
