| View previous topic :: View next topic |
| Author |
Message |
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
 Posted: Thu Dec 22, 2016 6:21 pm Post subject: Mate Marco memory leak? |
 |
|
I have recently installed Mate 1.16 with Gentoo stable. I leave it running for at least a week at a time before rebooting.
The last two weeks I have noticed that the memory consumption grows over the week ...from 30 MB up to 2.5GB.
I use the system monitor gui to follow the memory usage...see following picture:
https://imgur.com/a/CMNz6
I'm not sure if there is a bug for this issue, I haven't found anything about it.
Any ideas?
Thanks
Update:
I realized that my info wasn't complete...and the missing info is:
wine-staging
Sierrachart (windows charting program)
I use the above with Mate which seems to cause a unique memory consumption issue.
Last edited by davidbrooke on Sun Jan 22, 2017 4:07 am; edited 1 time in total |
|
| Back to top |
|
 |
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Thu Dec 22, 2016 7:06 pm Post subject: Re: Mate Marco memory leak? |
|
|
| davidbrooke wrote: | | The last two weeks I have noticed that the memory consumption grows over the week ...from 30 MB up to 2.5GB. |
davidbrooke ... as the saying goes "a page of unused RAM is wasted RAM", the fact that it increases is to be expected (under normal circumstances). Linux caches every page until that memory is needed, if its needed that page is then freed. That doesn't mean there isn't a memory leak, only that 'free' (or any similar tool) will show an increase in memory usage over time (noting 'buff/cache').
best ... khay |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Fri Dec 23, 2016 5:34 am Post subject: |
|
|
@khay
Now marco with compton has increased from 2.5 GB to 2.9 GB with the overall memory used at 84% or 6.5 GB.
In the past KDE plasma kwin or Gnome mutter didn't continually consume memory like I'm seeing now with Mate Marco.
Last edited by davidbrooke on Sun Jan 22, 2017 4:08 am; edited 1 time in total |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Fri Dec 23, 2016 11:33 pm Post subject: |
|
|
30 hours later....
Marco with compton has increased from 2.5 GB to 3.4 GB with the overall memory used at 96.4% or 7.5 GB.
Last edited by davidbrooke on Sun Jan 22, 2017 4:09 am; edited 1 time in total |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Tue Dec 27, 2016 10:04 pm Post subject: |
|
|
Marco with compton has increased from 30 MB to 3.6 GB during a 5 day span.
I have started testing on replacing Marco with Openbox...preliminary results are....Openbox doesn't increase in memory size.
Last edited by davidbrooke on Sun Jan 22, 2017 4:09 am; edited 1 time in total |
|
| Back to top |
|
|
The Main Man
Veteran
Joined: 27 Nov 2014
Posts: 1166
Location: /run/user/1000
|
| Posted: Wed Dec 28, 2016 12:18 am Post subject: |
|
|
| You can also try replacing it with compiz. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Sun Jan 01, 2017 4:04 pm Post subject: |
|
|
| kajzer wrote: | | You can also try replacing it with compiz. |
Please give me a bit more direction to use compiz.
I have seen several posts concerning what works and what doesn't... not sure which compiz to use.
Also dconf has changed in the latest version where it no longer allows me to substitute another window manager. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Sun Jan 01, 2017 9:00 pm Post subject: |
|
|
Interesting....
I went back and looked again at Dconf and the ability to change the window manager is still there....not much sleep this week....sorry.
Also I found the gsettings route that works as well as the command openbox --replace too. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Mon Jan 02, 2017 4:48 am Post subject: |
|
|
| kajzer wrote: | | You can also try replacing it with compiz. |
To make a long story as short as possible....
I tried three compiz sources:
1. Compiz 8 - Gentoo overlay
https://wiki.gentoo.org/wiki/Compiz
The wiki is a bit dated. I had to manually add the emerald package. For some reason the "x11-wm/compiz-fusion emerald" use flag wouldn't work correctly.
Compiz seemed to work ok but the emerald windows title bar / decorations options was limited.
2. Compiz 9 - desktop-effects overlay
http://wiki.mate-desktop.org/compiz
The wiki is a bit dated and the overlay is too. Version 0.9.13.1 is available at https://launchpad.net/compiz but the overlay would only allow version 0.9.8.6.
There was an error prior to compiling... couldn't find "FindCompiz.cmake". So compiz 9 wasn't installed.
3. Compiz 8 - compiz-reloaded-overlay (your overlay)
https://github.com/kajzersoze/compiz-reloaded-overlay
The info was accurate and the install worked as expected.
Compiz seemed to work ok and the emerald windows title bar / decorations was better than Gentoo overlay.
Thoughts for now:
*The existing windows title bar / decorations (Vertex-theme) was removed and I was forced to use the GTK or emerald options that was supplied by the compiz installation. None of the options were as good as the Vertex-theme that was initially installed. Is there a way to get the Vertex-theme back?
**There wasn't a need to replace the marco window manager since compiz came with a function to start and replace the current window manager called "fusion-icon". I just just added a simple entry in the auto start feature in Mate. So compiz becomes the window manager and the compositing begins at startup.
***I haven't yet tested for the memory issue since there was a bit of time involved in getting compiz installed.
****I'm new to compiz so my knowledge is limited. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Fri Jan 13, 2017 2:57 am Post subject: |
|
|
| davidbrooke wrote: | | Marco with compton has increased from 30 MB to 3.6 GB during a 5 day span. |
I tested Gnome 3 and the results were basically the same...gnome-shell memory increased at a parallel rate to Marco.
Currently I'm not sure if what i see is expected behavior or both are experiencing the same issue.
I will be testing Openbox next.
Last edited by davidbrooke on Sun Jan 22, 2017 4:10 am; edited 1 time in total |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Sun Jan 22, 2017 4:03 am Post subject: |
|
|
I tested Marco with the built-in compositing and Marco without the built-in compositing....and the results were the same as Marco with compton...increasing memory consumption.
I also tested Slackware KDE4 and kwin paralleled the Openbox results.
Lastly, I realized that I never mentioned that I have been using wine-staging and a charting program "Sierrachart", which are key to Marco memory consumption issue. I will update the first post to reflect it. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Fri Jan 27, 2017 10:37 pm Post subject: |
|
|
The results of my findings so far:
I conducted a test which reviewed the window manager's memory consumption when running wine and a windows program (SierraChart).
The test results show two possible outcomes:
1. Minimal memory consumption.
WM's that resulted this condition:
Kwin (KDE Plasma) started at 29 MB and ended at 44 MB during a 5 day span.
Kwin (KDE4) and Openbox (replacement for Marco in Mate) showed the same basic results as Kwin (KDE Plasma).
2. Continual memory consumption.
WM's that resulted this condition:
Marco (with or without a compositor) started at 30 MB and ended at 3.6 GB during a 5 day span.
Mutter / Gnome-shell also showed the same basic result as Marco
Setups tested:
Gentoo Gnome systemd
Arch Gnome systemd
Gentoo Mate
Gentoo Mate with Openbox as the window manager
Slackware KDE4
Gentoo KDE Plasma
Conclusions
The most basic result was that wine and the windows program were not the result of the memory issue. The test points toward certain window managers...Marco and Mutter as the probable problem areas that need attention to resolve the memory issue.
Notes
1. Swap had started being used at the end of the Marco test, since all available ram had been consumed.
2. Systemd was used where noted. |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Fri Jan 27, 2017 10:41 pm Post subject: |
|
|
My next step is to post a bug report to both Gnome and Mate. If anyone has any experience with bugs reports to Gnome and Mate...please advise so that I may give them exactly the info they need.
Thanks |
|
| Back to top |
|
|
|
Desktop Environments
