Bug 629 - Large memory usage in Gnome version.
: Large memory usage in Gnome version.
Status: RESOLVED INVALID
Product: Desktop Bugs
Classification: ROSA Desktop
Component: GNOME edition
: Marathon
: x86_64 Linux
: Normal normal
: ---
Assigned To: Denis Koryavov
: ROSA Linux Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-09 00:01 MSD by Postnikov Dmitry
Modified: 2012-08-28 11:28 MSD (History)
0 users

See Also:
RPM Package:
ISO-related:
Bad POT generating:
Upstream:


Attachments
mem1 (219.94 KB, image/png)
2012-08-09 00:01 MSD, Postnikov Dmitry
Details
mem2 (250.53 KB, image/png)
2012-08-09 00:01 MSD, Postnikov Dmitry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Postnikov Dmitry 2012-08-09 00:01:04 MSD
Created attachment 457 [details]
mem1

Description of problem:
ROSA 2012 Gnome iso image 387th.
After use in about 8 hours, the memory usage has reached a critical point. There are 4 gigabytes of RAM. Of these, 3.5 gigabytes of memory occupied by ROSA Gnome.
Where is clearly a memory leak.
See the attached files.
==============
[root@mindlife dima]# cat /proc/meminfo
MemTotal:        3542952 kB
MemFree:          195640 kB
Buffers:           43716 kB
Cached:          2484420 kB
SwapCached:         2572 kB
Active:           811032 kB
Inactive:        2317056 kB
Active(anon):     411496 kB
Inactive(anon):   201396 kB
Active(file):     399536 kB
Inactive(file):  2115660 kB
Unevictable:          16 kB
Mlocked:              16 kB
SwapTotal:       2047996 kB
SwapFree:        2042260 kB
Dirty:                72 kB
Writeback:             0 kB
AnonPages:        597892 kB
Mapped:            98148 kB
Shmem:             12940 kB
Slab:             110772 kB
SReclaimable:      89044 kB
SUnreclaim:        21728 kB
KernelStack:        2520 kB
PageTables:        24200 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     3819472 kB
Committed_AS:    1712556 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      303916 kB
VmallocChunk:   34359431836 kB
HardwareCorrupted:     0 kB
AnonHugePages:    116736 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:       93760 kB
DirectMap2M:     3575808 kB
DirectMap1G:           0 kB
[root@mindlife dima]#
====================

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Postnikov Dmitry 2012-08-09 00:01:19 MSD
Created attachment 458 [details]
mem2
Comment 2 Denis Koryavov 2012-08-09 10:50:30 MSD
Please, use a ps_mem.py script http://www.pixelbeat.org/scripts/ps_mem.py.
Comment 3 Postnikov Dmitry 2012-08-09 11:31:45 MSD
(In reply to comment #2)
> Please, use a ps_mem.py script http://www.pixelbeat.org/scripts/ps_mem.py.

1. The new version moved to github https://github.com/pixelb/scripts/tree/master/scripts
2. Are you saying that built-in system does not provide a complete "picture" of the works system?
Comment 4 Denis Koryavov 2012-08-10 16:23:09 MSD
Well, yes. But there is one point: system can reserve many memory for closed application (just not free it) if it still have some free memory. If not, then it will free memory. Thus, you can see that system uses much more memory than in reality.
Comment 5 Postnikov Dmitry 2012-08-11 21:11:48 MSD
I understand. Then, how do you know the real memory consumption? Without asleep applications.
ps_mem.py and htop and top give very different figures. For example:
ps_mem - 754Mb
htop - 762Mb
top - 3.3Gb
Who to believe?
Comment 6 Denis Koryavov 2012-08-13 16:57:31 MSD
I suppose that ps_mem shows better results.
Comment 7 Denis Koryavov 2012-08-28 11:28:35 MSD
OK, I close this bug as invalid.