View Issue Details

IDProjectCategoryView StatusLast Update
0002588Kali LinuxKali Package Bugpublic2015-09-03 09:24
Reporterlillypad Assigned Torhertzog  
Status closedResolutionwon't fix 
Product Versionkali-dev 
Summary0002588: Kali Linux 2.0 gnome-shell Memory Leak

Currently Kali Linux 2.0 is using Gnome 3.14.1.

There is currently a bug tracker for this issue here:

and here:

Opening the terminal seems to be causing the issue, after doing many commands in terminal the memory for gnome-shell goes up very quickly doing normal tasks.

There is a temporary solution by doing ALT + F2, 'r', <ENTER>. This will reset gnome 3.14.1 and remove the excess memory which has leaked. A less than ideal solution however it's one to keep others using the distribution effectively over many hours not requiring a reboot.

The memory leak isn't as bad as previous versions of Gnome however it's still preset sometimes taking up 10 percent of the ram on a 5GB Ram system. I took a base line it was around 3.73 percent and should only be using 190mb - 200mb of ram if all windows are closed however this isn't the case.

Hoping this will help others with the memory leak issue as well. I know gnome 3.16 has been release and not sure if this will fix the memory leak issue in 3.14.1 but it's a possibility to look into.

This issue should be looked at as more serious for those who use the distribution for many hours of the day.

Steps To Reproduce
  1. Open up terminal
  2. Do repetitive tasks in terminal
  3. Close terminals when done
  4. Notice how memory doesn't go down in gnome-shell
  5. Reset Memory by doing ALT + F2, 'r', <ENTER>.




2015-08-23 12:30

reporter   ~0003827

You can also find a record of this issue here:



2015-09-03 09:24

administrator   ~0003884

I'm afraid that such a bug report is not very actionable. And we already have gnome 3.16 lined up for the next release.

If anything such issues must be reported and fixed in the upstream software that does leak memory... and not here unless you can point us to a working patch that we should apply in our current version.

Issue History

Date Modified Username Field Change
2015-08-23 12:24 lillypad New Issue
2015-08-23 12:30 lillypad Note Added: 0003827
2015-09-03 09:24 rhertzog Note Added: 0003884
2015-09-03 09:24 rhertzog Status new => closed
2015-09-03 09:24 rhertzog Assigned To => rhertzog
2015-09-03 09:24 rhertzog Resolution open => won't fix