Turns out after a fresh reboot the memory usage isn't much different
after I close all apps and VmData for gnome shell is only about 400MB.
So, perhaps this isn't the smoking gun I thought it was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks @vanvugt, this was helpful. I'm running ubuntu 23.10. It's been
about a week since I rebooted and I noticed swap usage was quite high.
I've got 32GB of RAM and am a developer with a bunch of stuff open at
once. Decided to investigate. Closed everything, but left just gnome
running and a
Still happening on Ubuntu 18.04.6: gnome-shell 3.28.4:
KiB Mem : 20210320 total, 5287136 free, 9839436 used, 5083748 buff/cache
KiB Swap: 38653948 total, 35113980 free, 3539968 used. 9823860 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
FWIW, I have a pretty consistent reproduction of this on my 20.04
machine here. Restarting gnome-shell with Alt-F2 then "r" causes all
the window management stuff to go away, but doesn't actually kill the
process that's reporting the giant resident set size. Manually killing
that pid also causes
** Tags removed: artful zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage notifications about this bug go to:
** Changed in: gjs (Ubuntu)
Assignee: (unassigned) => Hassan Kibiti (kibitih)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
I don't know what I was thinking... This bug is clearly declared fixed
in 18.04 already:
gjs (1.52.1-1ubuntu1) bionic; urgency=medium
* Add fix-crashes-lp1763878-revert-575f1e2e077.patch to fix shutdown
crashes (LP: #1763878)
* Add some patches to solve large memory leaks (LP: #1672297)
This bug is fixed in Ubuntu 18.10, but beware 18.10 also brings a new
separate leak: bug 1800165.
This bug is not yet fixed in Ubuntu 18.04 because the fix for this one
also causes a performance regression in 18.10 that we don't want to
repeat in 18.04:
I switched from nvidia driver to nouveau driver and the huge memory
usage disappeared. Small jumps (increase) in memory usage stayed with
us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
** Changed in: gjs (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
No comment...
** Attachment added: "screenshot of gnome-usage"
https://bugs.launchpad.net/gnome-shell/+bug/1672297/+attachment/5190499/+files/Screenshot%20from%202018-09-19%2011-33-32.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Gnome 3.30 is out. Are there any ETA or plan to fix this Critical issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
I installed Ubuntu 18.10 gjs and libgjs0g 1.53.3-1 (of Ubuntu 18.10) to
Ubuntu 18.04. It seems that the memory leak lives forever...
Memory usage started from 170MB, and after two hours is over 360MB.
[image: Képernyőkép erről: 2018-09-02 23-46-44.png]
chris pollock <1672...@bugs.launchpad.net>
This is:
apt-cache policy gnome-shell
gnome-shell:
Installed: 3.28.2-0ubuntu0.18.04.1
Candidate: 3.28.2-0ubuntu0.18.04.1
apt-cache policy evolution
evolution:
Installed: 3.28.1-2
Candidate: 3.28.1-2
lsb_release -crid
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:
Yesterday I discovered another Gnome software bug, (another) one of
Files (Nautilus). Without any reason, Files was running 4+% of the CPU
for a long time, without even touching it. Might be some interaction, if
I see that again, will file a separate bug report.
--
You received this bug
Will all these memory bleed issues be patched in the upcoming 18.04.1
LTS release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Can we PLEASE get some kind of coherent update on this for bionic. Most
distros (debian unstable, arch) already incorporated this fix. Is this
fix coming? Is any part of it coming? This is issues is serious enough
that it needs addressing, please respond!
--
You received this bug notification
Ubuntu 18.04.1 is coming soon (tomorrow?). What about the bug fixes?
I know a temporary method, but it is not so nice (but it works, saves
~400MB RAM): run after login
sudo killall -u gdm
killall gnome-software
One more, clear gnome-calendar. It launches automatically, uses
constantly 2-400MB
Well for this bug I need to install Xubuntu and lightdm, run very fast
with no issues, BUT looks like Firefox is eating a lot of RAM in both
desktops, for my job I need FF to be opened all the time, so the time to
time I need to close it and relaunch it, if not FF freezing my desktop,
now even
I recently changed my Ubuntu 18.04 installation to use i3 window manager
due to this issue, but alas, it's not enough, as GNOME is used for my
login screen. After 3 days away from my desk, the memory is 38.2G/39.2G
and swap is 14.6/22.4G and the /usr/bin/gnome-shell process owned by gdm
has taken
@ Nick Timkovich
The 'fix released' for 18.04 (1.52.1-1ubuntu1) is to the extent as seen in
comment 78 which may not be as developed as the 'fix released' for 18.10 , i.e
comment 96
The bionic task for gjs as shown at top still says 'In progress' which *may*
mean there are further gjs patches
For us end-users, does "Fix Released" just mean released to a
nightly/unstable/private package repo? Because
https://packages.ubuntu.com/bionic/gjs still lists the version at
1.52.1, that means this still unreleased in stable?
What's the status to look out for when an `apt-get upgrade` will fix
Laney,
Thanks for doing the work. I know that you know...
My main concern is about effective communication with the 141 users
subscribed here. And that means using a correct status value which I am
happy to do manually.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gjs (Ubuntu)
Assignee: Ubuntu Desktop (ubuntu-desktop) => (unassigned)
** Changed in: gjs (Ubuntu Bionic)
Assignee: Ubuntu Desktop (ubuntu-desktop) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, in this instance Simon had quoted this bug reference in the
changelog for a previous version:
https://tracker.debian.org/news/958430/accepted-gjs-1523-2-source-
into-unstable/
lucky :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package gjs - 1.53.3-1
---
gjs (1.53.3-1) experimental; urgency=medium
[ Simon McVittie ]
* d/watch: Watch for development releases
* New upstream development release
[ Iain Lane ]
* New upstream development releases 1.53.2 and 1.53.3
-- Iain
On Wed, Jul 04, 2018 at 09:30:05AM -, Daniel van Vugt wrote:
> Technically, being in cosmic-proposed only makes it Fix Committed. Not
> yet Fix Released.
Daniel, I know this, but syncpackage marks bugs as Fix Released and it's
manual work to go back and change it because nothing will do that
Technically, being in cosmic-proposed only makes it Fix Committed. Not
yet Fix Released.
** Changed in: gjs (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gjs (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Ubuntu Desktop (ubuntu-desktop)
** Changed in: gjs (Ubuntu Bionic)
Assignee: Daniel van Vugt (vanvugt) => Ubuntu Desktop (ubuntu-desktop)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package gjs - 1.53.3-1
---
gjs (1.53.3-1) experimental; urgency=medium
[ Simon McVittie ]
* d/watch: Watch for development releases
* New upstream development release
[ Iain Lane ]
* New upstream development releases 1.53.2 and 1.53.3
-- Iain
I think the cleanest first step will be -> bug 1778660
That will allow us to drop the patches we're carrying and also get in
sync with Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
It appears the only gjs fixes we are missing are:
https://gitlab.gnome.org/GNOME/gjs/merge_requests/121
https://gitlab.gnome.org/GNOME/gjs/merge_requests/122
However the first is more to do with performance, and a little to do
with memory usage. It's also included in upstream gjs releases
It's on the (backlog) queue: https://trello.com/b/3VYBPFaR/ubuntu-
desktop-1810-cycle
Although this doesn't need to wait for me. Anyone could cherry pick and
propose the remaining fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
https://gitlab.gnome.org/GNOME/gjs/merge_requests/122 is now merged, all
the other merge requests linked to in https://gitlab.gnome.org/GNOME
/gnome-shell/issues/64 are now merged. Daniel could we have soon have a
-proposed package of backports of these fixes up for testing? :)
--
You received
After some minutes I logged in (Ubuntu 18.04, gnome-shell) something used a lot
of memory (approx. 1GB). I checked gnome-system-monitor, but there was not any
process which used more memory as usual (neither user nor system). Nothing was
opened or launched. Only one thing helped: logout and
Looks like we're still waiting for upstream to land:
https://gitlab.gnome.org/GNOME/gjs/merge_requests/122
from the list:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any news on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage notifications about this bug go to:
I am unsubscribing ubuntu-sponsors since I don't see anything here now
that is ready for sponsoring. Please feel free to resubscribe when you
have something else that needs sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Let's keep this open till we have the full set up upstream fixes in Ubuntu:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
** Changed in: gjs (Ubuntu Bionic)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And you should... SEE THIS LINK
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773 which is the
most important memory leak and I posted it 3 years ago, could be possible that
just ONE developer take this seriously?
--
You received this bug notification because you are a
Yep, that's about ignorant gnome-shell team and really outdated toolkit.
Ubuntu should use KDE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and
Guys, i am not programmer, but i`m wander why gnome have so many memory
leaks? Most of them have been known for years and nobody cares till
Ubuntu LTS 18.04 release. Bad code, bad programming, or other reason?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
If you really want to close this bug PLEASE WATCH THIS
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell
I wonder if we should keep using this bug as the additional leak fixes
land in future?
Leaks are likely to come and go indefinitely over time as the code
changes, so we should try to decide the acceptance criteria for closing
this bug. And when it would be more appropriate to open new similar
This bug was fixed in the package gjs - 1.52.1-1ubuntu1
---
gjs (1.52.1-1ubuntu1) bionic; urgency=medium
* Add fix-crashes-lp1763878-revert-575f1e2e077.patch to fix shutdown
crashes (LP: #1763878)
* Add some patches to solve large memory leaks (LP: #1672297)
-
Rocko,
the other thing to consider is that the patch in comment #68 stops all
types of GObject leaks, including those holding resources outside of
normal memory. So if for example that texture leak returns (which I
expect it may), that will consume texture memory even faster than you
see main
Yes, we know that is only one of the leak fixes. The other fixes
(upstream, not reviewed yet) are less mature and have not been included
in the Ubuntu patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems not committed anywhere yet.
** Changed in: gjs (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots
I managed to build and install a patched gjs last night thanks to a
helpful hint from a fellow user (ie to use debuild -us -uc -b to build
it instead of make and make install).
Initially, gnome-shell was using around 170 MB according to gnome-
system-monitor (atop says consistently says it is
Glad to see that this bug is about to be squished...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage notifications about
** Changed in: gjs (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To
Yes, many Ubuntu packages are customized and often don't work unless you
use the same customization options in your build. You can find out what
those are by running 'apt-get source FOO' and then looking in
debian/rules. However it's too complicated to write a clear guide for.
Also, it sounds
Well, quite. I built and installed it with "./configure --prefix=/usr &&
make && sudo make install" and it's obviously more complicated than
that. Is there a guide somewhere for how to build and install gnome-
shell and its components in ubuntu?
--
You received this bug notification because you
Sounds like you might have made a mistake. Just wait till the patch is
released properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows
Is that patch getting into Ubuntu soon? I tried applying it to the
latest gjs source package and installing the patched package, but it
left gdm in an un-startable state, even when I uninstalled it and
reinstalled the default gjs package.
--
You received this bug notification because you are a
Here's a patch to fix the biggest of the leaks.
I notice however that upstream is working on additional fixes. But those
fixes are very new and experimental. What I am providing here is the
more significant and mature of the leak fixes currently being proposed.
** Patch added:
** No longer affects: gnome-shell (Ubuntu Bionic)
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows
** Changed in: gjs (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: gjs (Ubuntu Bionic)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
@cement_head: The desktop team agrees. We'll be releasing *something*
for this bug this week. Only 3 days to final freeze...
@Amr: Those are probably better left as separate bugs to this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Upstream has released new versions of accountsservice & polkit to fix some
leaks.
https://cgit.freedesktop.org/accountsservice/tag/?h=0.6.46
https://cgit.freedesktop.org/polkit/tag/?h=0.114
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In my opinion, Ubuntu 18.04 should not be released until this is fixed -
it should be delayed if required. This is O/S killer and will do more
to damage the brand name of Ubuntu than releasing a deeply flawed, not-
ready-for-prime-time, version. Frankly, Ubuntu 18.04 is unusable as an
LTS with
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gjs (Ubuntu Bionic)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, when a fix lands we will push it into 18.04 as a priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
Could the eventual fix be cherry-picked for Ubuntu's GNOME 3.28? Merge
requests 114 and 50 (gjs; upstream) are targeted for GNOME 3.30.0 (for
example) yet presumably Ubuntu would want the fix in Ubuntu 18.04 rather
than shipping with the leak?
--
You received this bug notification because you
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
** Changed in: gjs (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
My efforts from last week ran into a dead end because I can't reproduce
that massive texture leak any more.
I can however still reproduce the original "smaller" leak (0.5-1.0MB per
overview) this bug was about in the first place. And good news:
Upstream's experimental fix seems to work:
Yes I imagine gnome-shell contains multiple different leaks. Each
different leak will get a different upstream bug and a different fix.
So this bug may stay open indefinitely as more and more people jump on
board. Or we may have to cut it off at some point and use other bug
reports for specific
It does not just happen when opening the main overview.
Even when you click on the network/volume/power panel applet and the
pop-up opens, the memory usage increases.
Just repeatedly click on the network/volume/power panel applet and watch
gnome-shell memory usage grow in system monitor with
Thanks for the hints.
I have created a visual profile of the the main overview-related leaks here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: mutter (Ubuntu Bionic)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Tags removed: rls-bb-incoming
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => In Progress
** Changed in: mutter (Ubuntu)
I think my report is related:
https://bugzilla.gnome.org/show_bug.cgi?id=787983
** Bug watch added: GNOME Bug Tracker #787983
https://bugzilla.gnome.org/show_bug.cgi?id=787983
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Disabling Gnome3 Shell Extensions is not the answer. Solving the
underlying bug is the answer. Disabling the G3X will severe cramp
usability of G3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I posted the bug 3 years ago in 2015 and yesterday the bug expired
because nobody saw it, what a irony
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@borovaka: That also matches my experience: If you disable everything
that creates previews the gnome-shell's memory usage will grow slower.
But if you only have 4 Gigabytes of memory you still have to reboot your
computer every 2 hours.
--
You received this bug notification because you are a
Sometimes I get the impression that they seem not to be using the newer
gnome-shell as their daily driver, as it is quite impossible not to see
this happening. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually it is not only "window preview" problem.
It is related to mozjs garbage collector (I think).
You can follow the issue on gnome gitlab:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
And I was wondering why 2 years ago 0,5 Gigabytes of RAM was plentiful
for 32bit and now 4 Gigabytes on 64 bit is too little. Let's hope the
window preview problem gets resolved soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is also a nice video demonstrating the issue:
https://www.youtube.com/watch?v=zQCOO-9HZvU
It runs Fedora, but the behaviour is exactly the same on Bionic as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-shell
Status: Unknown => Confirmed
** Changed in: gnome-shell
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
@vanvugt could you try the steps I posted in #46. I can reliably
reproduce this on a clean install of Bionic daily in a VM. No extra
extensions, just opening window previews with Super multiple times (two
windows open).
Thank you.
--
You received this bug notification because you are a member
It might have been fixed in a series of changes made in mutter (future
version) 3.26.3. It's just unusual and unexpected that Gnome has not
done a release for months, so we have not yet tried those fixes.
Instead, it looks like we will jump to 3.28 now, soon. So if bionic goes
well with 3.28 then
^ dependency: sudo apt-get install xprintidle
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage notifications about this
Its amazing that so many people have this issue and this bug has not yet
been fixed. Anyway here's my (reset when idle) workaround (use at your
own risk, may have bugs etc.):
https://pastebin.com/8ypFBjQ0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There is a memory leak generating window previews on gnome shell and
since pressing the Super key generates windows previews the memory usage
grows exponentially. For me Gnome Shell eats about 100-150 MB every day
I leave it running.
I tested this both on an Intel graphics machine and on a VM, in
PS: and please bring back the Wifi connections list to the menu and add
a thick to activate "View inserted password"; see this
https://www.youtube.com/watch?v=n2UbE2xh1Q0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It might be more complicated to fix as there are lots and lots of
actions that get to memory leaks. There are some crashes, too. Bad
programming, probably, and it might need some fundamental changes in the
code and architecture. They are creating lists and objects that are
larger and larger on
If we find a fix that works, then yes it will be backported to 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
So does that mean this is a wontfix for 17.10, the current version?
I had to double my RAM to 16GB just to get more than a day out of gnome-
shell at work, otherwise as the day goes on, each notification I receive
hangs the system for a few seconds and locking and unlocking the screen
can take up
See also comment #29. It's probably not worth commenting further here
till we're on at least version 3.26.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of
Just noticed it in updated Bionic. After boot uses around 450MB of VRAM
and then suddenly jumps to 1200MB and more when only Chrome is running.
When Chrome is closed it does not change. Using Geforce 960 GTX with 390
drivers. Freezes and also black streak flashes on one of monitors
sometimes. When
Yes, I got some freezes, too, even longer than 10 seconds. One time I
restarted the laptop as I did not know what is going on, another time at
some point Gnome crashed and started by itself. This did not happen in
Unity.
--
You received this bug notification because you are a member of Ubuntu
The entire UI lags far behind as well. When gnome-shell using around 500
MB RAM, middle clicking Nautilus freezes the entire system UI for up to
10 seconds. No mouse, no keyboard, no clicking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
VmData: 636560 kB 10:30
VmData: 848276 kB 15:45
That's up 33% in 5.25 hours, during which I wasn't interacting with the
computer, so there shouldn't have been any demands on gnome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It's important to remember that RSS increases is no indication of a leak
- it will rise and fall according to how busy the machine is and not how
much new memory the process has allocated. Please ignore all RSS values
as they are going to be unpredictable and misleading.
As for VSZ, that's kind
If I press the Ubuntu key over and over, showing the overview of all the
desktops, and then again to return to the normal view of the current
desktop, RSS for gnome-desktop increases rapidly (measurements taken at
15-second intervals.
USER PID %CPU %MEMVSZ RSS TTY STAT START
I'm trying to track down something that makes system performance degrade
in less than an hour. Whenever I switch desktops, move my cursor to a
place where a tooltip is displayed, open a pull-down menu, the display
freezes for 5-15 seconds before, for example, the menu or tooltip is
released.
If I
Regarding #32, The total shown is 16,293,840 and used is 1,781,036,
which is about 11% of the total, not more than total. (With that many
digits, commas help.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also seen on AskUbuntu - https://askubuntu.com/q/1001069/66509 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
1 - 100 of 123 matches
Mail list logo
