Lowering Compiz memory usage





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







36















I have been following the updates that appear every week in how they affect the performance and resource usage of Compiz since I installed 11.10 (Right now I am testing 12.04 and 14.04). For what I have seen, the CPU and memory usage have lowered (specially memory). I am comparing installing 12.04/14.04 without any updates and then applying all updates and also comparing 12.04 to 14.04. For example nautilus is using less than 35 MB (For me it was between 70 MB and 150 MB doing the same activities with it several versions ago).



Other processes have also received some kind of optimizations which have lowered my total memory usage from around 850 MB to 610 MB (I also use services like Apache, MySQL, etc..) but after all of this time, the only one that has stayed almost the same is Compiz. It still uses more than 100MB to start. Only using the desktop with Unity and no other programs running, it takes (right now) 133 MB. What options can I use to lower the memory footprint WITHOUT compromising the stability of Unity (For example removing the OpenGL plugin from Compiz config is a BAD idea).



What optimizations can be done to lower the memory usage of Compiz?



NOTE - I have Compiz Config Settings Manager (CCSM) installed already.










share|improve this question

























  • Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

    – Anonymous
    Nov 25 '11 at 18:43











  • @Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

    – Luis Alvarado
    Nov 25 '11 at 18:50











  • +1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

    – Mark Rooney
    Nov 25 '11 at 22:30


















36















I have been following the updates that appear every week in how they affect the performance and resource usage of Compiz since I installed 11.10 (Right now I am testing 12.04 and 14.04). For what I have seen, the CPU and memory usage have lowered (specially memory). I am comparing installing 12.04/14.04 without any updates and then applying all updates and also comparing 12.04 to 14.04. For example nautilus is using less than 35 MB (For me it was between 70 MB and 150 MB doing the same activities with it several versions ago).



Other processes have also received some kind of optimizations which have lowered my total memory usage from around 850 MB to 610 MB (I also use services like Apache, MySQL, etc..) but after all of this time, the only one that has stayed almost the same is Compiz. It still uses more than 100MB to start. Only using the desktop with Unity and no other programs running, it takes (right now) 133 MB. What options can I use to lower the memory footprint WITHOUT compromising the stability of Unity (For example removing the OpenGL plugin from Compiz config is a BAD idea).



What optimizations can be done to lower the memory usage of Compiz?



NOTE - I have Compiz Config Settings Manager (CCSM) installed already.










share|improve this question

























  • Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

    – Anonymous
    Nov 25 '11 at 18:43











  • @Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

    – Luis Alvarado
    Nov 25 '11 at 18:50











  • +1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

    – Mark Rooney
    Nov 25 '11 at 22:30














36












36








36


17






I have been following the updates that appear every week in how they affect the performance and resource usage of Compiz since I installed 11.10 (Right now I am testing 12.04 and 14.04). For what I have seen, the CPU and memory usage have lowered (specially memory). I am comparing installing 12.04/14.04 without any updates and then applying all updates and also comparing 12.04 to 14.04. For example nautilus is using less than 35 MB (For me it was between 70 MB and 150 MB doing the same activities with it several versions ago).



Other processes have also received some kind of optimizations which have lowered my total memory usage from around 850 MB to 610 MB (I also use services like Apache, MySQL, etc..) but after all of this time, the only one that has stayed almost the same is Compiz. It still uses more than 100MB to start. Only using the desktop with Unity and no other programs running, it takes (right now) 133 MB. What options can I use to lower the memory footprint WITHOUT compromising the stability of Unity (For example removing the OpenGL plugin from Compiz config is a BAD idea).



What optimizations can be done to lower the memory usage of Compiz?



NOTE - I have Compiz Config Settings Manager (CCSM) installed already.










share|improve this question
















I have been following the updates that appear every week in how they affect the performance and resource usage of Compiz since I installed 11.10 (Right now I am testing 12.04 and 14.04). For what I have seen, the CPU and memory usage have lowered (specially memory). I am comparing installing 12.04/14.04 without any updates and then applying all updates and also comparing 12.04 to 14.04. For example nautilus is using less than 35 MB (For me it was between 70 MB and 150 MB doing the same activities with it several versions ago).



Other processes have also received some kind of optimizations which have lowered my total memory usage from around 850 MB to 610 MB (I also use services like Apache, MySQL, etc..) but after all of this time, the only one that has stayed almost the same is Compiz. It still uses more than 100MB to start. Only using the desktop with Unity and no other programs running, it takes (right now) 133 MB. What options can I use to lower the memory footprint WITHOUT compromising the stability of Unity (For example removing the OpenGL plugin from Compiz config is a BAD idea).



What optimizations can be done to lower the memory usage of Compiz?



NOTE - I have Compiz Config Settings Manager (CCSM) installed already.







compiz memory-usage optimization






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 23 '14 at 19:33







Luis Alvarado

















asked Nov 25 '11 at 18:37









Luis AlvaradoLuis Alvarado

147k139487658




147k139487658













  • Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

    – Anonymous
    Nov 25 '11 at 18:43











  • @Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

    – Luis Alvarado
    Nov 25 '11 at 18:50











  • +1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

    – Mark Rooney
    Nov 25 '11 at 22:30



















  • Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

    – Anonymous
    Nov 25 '11 at 18:43











  • @Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

    – Luis Alvarado
    Nov 25 '11 at 18:50











  • +1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

    – Mark Rooney
    Nov 25 '11 at 22:30

















Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

– Anonymous
Nov 25 '11 at 18:43





Disable some Compiz plugins that you do not need. You can do this with compizconfig-settings-manager. sudo apt-get install ccsm then run ccsm.

– Anonymous
Nov 25 '11 at 18:43













@Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

– Luis Alvarado
Nov 25 '11 at 18:50





@Anonymous - I already have ccsm installed and as I mention the Unity plugin and OpenGL plugins in the question I thought there was no need to say I had it installed. Either way am asking what optimizations to do in ccsm, gconf or any other.

– Luis Alvarado
Nov 25 '11 at 18:50













+1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

– Mark Rooney
Nov 25 '11 at 22:30





+1 for the question Luis - since doing all the regular updates to 11.10 I can no longer use Unity on my netbook - worked fine before on a fresh install. It is only compiz slowing my system down as Unity 2D and Gnome Shell work perfectly.....

– Mark Rooney
Nov 25 '11 at 22:30










3 Answers
3






active

oldest

votes


















18














It is rather difficult in my experience to lower the Compiz memory usage. The best thing I can suggest to lower the texture quality in the OpenGL plugin, but this won't change much afaik.



Another source of compiz memory increases can be memory leaks. This seems to sometimes be triggered by indicators, but can be from other sources as well (not sure of them yet).



My solution as been to periodically restart unity, using a simple script that contains:



#kill compiz completely, including all child processes, freeing it's memory:
killall -9 compiz &
#run unity and give you back a free terminal.
unity & disown


I know this isn't the best of answers, so I'm following this question myself to see if anyone has better tips.






share|improve this answer





















  • 3





    do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

    – ivotron
    May 28 '13 at 22:59






  • 1





    @ivotron unfortunately not. I'll seek a solution though.

    – RolandiXor
    May 29 '13 at 5:02






  • 2





    Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

    – Carlton
    Oct 14 '14 at 12:31



















20














A work around to the compiz memory leak is to:



sudo kill -HUP <compiz_process_id>


Not a great solution, but it frees up leaked memory without completely killing the process.






share|improve this answer


























  • Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

    – dpb
    Nov 27 '13 at 16:47













  • This should be the accepted answer.

    – jcalfee314
    Dec 30 '14 at 18:12






  • 2





    sudo kill -HUP $(pgrep compiz)

    – isaaclw
    Oct 2 '15 at 21:39






  • 8





    @isaaclw, or pkill -HUP compiz

    – Piotr Findeisen
    Dec 29 '15 at 2:59













  • thanks. It at least I do not need to restart the whole X.

    – Mohamad
    Mar 23 '17 at 8:29



















9














I know this is an old post, but Gus's answer helped me and I'd like to add to it. This is what I did (on Ubuntu 12.04):





  • Alt+F2 (run application)

  • Scheduled Tasks

  • New recurrent task

  • killall compiz -HUP

  • Every day at 00:00


Now compiz will be restarted automatically every night, without having to know the process id.



My problem was that if I left my screen locked for a few days, it took ~30 seconds to open the screen lock, and compiz memory usage was around 1000 MB.






share|improve this answer





















  • 1





    On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

    – Luís de Sousa
    Feb 12 '15 at 15:10












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f82684%2flowering-compiz-memory-usage%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









18














It is rather difficult in my experience to lower the Compiz memory usage. The best thing I can suggest to lower the texture quality in the OpenGL plugin, but this won't change much afaik.



Another source of compiz memory increases can be memory leaks. This seems to sometimes be triggered by indicators, but can be from other sources as well (not sure of them yet).



My solution as been to periodically restart unity, using a simple script that contains:



#kill compiz completely, including all child processes, freeing it's memory:
killall -9 compiz &
#run unity and give you back a free terminal.
unity & disown


I know this isn't the best of answers, so I'm following this question myself to see if anyone has better tips.






share|improve this answer





















  • 3





    do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

    – ivotron
    May 28 '13 at 22:59






  • 1





    @ivotron unfortunately not. I'll seek a solution though.

    – RolandiXor
    May 29 '13 at 5:02






  • 2





    Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

    – Carlton
    Oct 14 '14 at 12:31
















18














It is rather difficult in my experience to lower the Compiz memory usage. The best thing I can suggest to lower the texture quality in the OpenGL plugin, but this won't change much afaik.



Another source of compiz memory increases can be memory leaks. This seems to sometimes be triggered by indicators, but can be from other sources as well (not sure of them yet).



My solution as been to periodically restart unity, using a simple script that contains:



#kill compiz completely, including all child processes, freeing it's memory:
killall -9 compiz &
#run unity and give you back a free terminal.
unity & disown


I know this isn't the best of answers, so I'm following this question myself to see if anyone has better tips.






share|improve this answer





















  • 3





    do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

    – ivotron
    May 28 '13 at 22:59






  • 1





    @ivotron unfortunately not. I'll seek a solution though.

    – RolandiXor
    May 29 '13 at 5:02






  • 2





    Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

    – Carlton
    Oct 14 '14 at 12:31














18












18








18







It is rather difficult in my experience to lower the Compiz memory usage. The best thing I can suggest to lower the texture quality in the OpenGL plugin, but this won't change much afaik.



Another source of compiz memory increases can be memory leaks. This seems to sometimes be triggered by indicators, but can be from other sources as well (not sure of them yet).



My solution as been to periodically restart unity, using a simple script that contains:



#kill compiz completely, including all child processes, freeing it's memory:
killall -9 compiz &
#run unity and give you back a free terminal.
unity & disown


I know this isn't the best of answers, so I'm following this question myself to see if anyone has better tips.






share|improve this answer















It is rather difficult in my experience to lower the Compiz memory usage. The best thing I can suggest to lower the texture quality in the OpenGL plugin, but this won't change much afaik.



Another source of compiz memory increases can be memory leaks. This seems to sometimes be triggered by indicators, but can be from other sources as well (not sure of them yet).



My solution as been to periodically restart unity, using a simple script that contains:



#kill compiz completely, including all child processes, freeing it's memory:
killall -9 compiz &
#run unity and give you back a free terminal.
unity & disown


I know this isn't the best of answers, so I'm following this question myself to see if anyone has better tips.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 5 '13 at 15:17









Amanda

4,350104386




4,350104386










answered Nov 25 '11 at 19:08









RolandiXorRolandiXor

44.9k26140232




44.9k26140232








  • 3





    do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

    – ivotron
    May 28 '13 at 22:59






  • 1





    @ivotron unfortunately not. I'll seek a solution though.

    – RolandiXor
    May 29 '13 at 5:02






  • 2





    Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

    – Carlton
    Oct 14 '14 at 12:31














  • 3





    do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

    – ivotron
    May 28 '13 at 22:59






  • 1





    @ivotron unfortunately not. I'll seek a solution though.

    – RolandiXor
    May 29 '13 at 5:02






  • 2





    Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

    – Carlton
    Oct 14 '14 at 12:31








3




3





do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

– ivotron
May 28 '13 at 22:59





do you know how to restart compiz without screwing up the location of the windows in their workspaces. After I kill compiz all the windows move to the first workspace and I have to reorganize them, which is a pain

– ivotron
May 28 '13 at 22:59




1




1





@ivotron unfortunately not. I'll seek a solution though.

– RolandiXor
May 29 '13 at 5:02





@ivotron unfortunately not. I'll seek a solution though.

– RolandiXor
May 29 '13 at 5:02




2




2





Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

– Carlton
Oct 14 '14 at 12:31





Worked for me although I got a little nervous when nothing was showing on my desktop for a few seconds :)

– Carlton
Oct 14 '14 at 12:31













20














A work around to the compiz memory leak is to:



sudo kill -HUP <compiz_process_id>


Not a great solution, but it frees up leaked memory without completely killing the process.






share|improve this answer


























  • Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

    – dpb
    Nov 27 '13 at 16:47













  • This should be the accepted answer.

    – jcalfee314
    Dec 30 '14 at 18:12






  • 2





    sudo kill -HUP $(pgrep compiz)

    – isaaclw
    Oct 2 '15 at 21:39






  • 8





    @isaaclw, or pkill -HUP compiz

    – Piotr Findeisen
    Dec 29 '15 at 2:59













  • thanks. It at least I do not need to restart the whole X.

    – Mohamad
    Mar 23 '17 at 8:29
















20














A work around to the compiz memory leak is to:



sudo kill -HUP <compiz_process_id>


Not a great solution, but it frees up leaked memory without completely killing the process.






share|improve this answer


























  • Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

    – dpb
    Nov 27 '13 at 16:47













  • This should be the accepted answer.

    – jcalfee314
    Dec 30 '14 at 18:12






  • 2





    sudo kill -HUP $(pgrep compiz)

    – isaaclw
    Oct 2 '15 at 21:39






  • 8





    @isaaclw, or pkill -HUP compiz

    – Piotr Findeisen
    Dec 29 '15 at 2:59













  • thanks. It at least I do not need to restart the whole X.

    – Mohamad
    Mar 23 '17 at 8:29














20












20








20







A work around to the compiz memory leak is to:



sudo kill -HUP <compiz_process_id>


Not a great solution, but it frees up leaked memory without completely killing the process.






share|improve this answer















A work around to the compiz memory leak is to:



sudo kill -HUP <compiz_process_id>


Not a great solution, but it frees up leaked memory without completely killing the process.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 13 at 8:49









Olorin

1




1










answered Jul 24 '13 at 10:54









Gus WestGus West

20122




20122













  • Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

    – dpb
    Nov 27 '13 at 16:47













  • This should be the accepted answer.

    – jcalfee314
    Dec 30 '14 at 18:12






  • 2





    sudo kill -HUP $(pgrep compiz)

    – isaaclw
    Oct 2 '15 at 21:39






  • 8





    @isaaclw, or pkill -HUP compiz

    – Piotr Findeisen
    Dec 29 '15 at 2:59













  • thanks. It at least I do not need to restart the whole X.

    – Mohamad
    Mar 23 '17 at 8:29



















  • Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

    – dpb
    Nov 27 '13 at 16:47













  • This should be the accepted answer.

    – jcalfee314
    Dec 30 '14 at 18:12






  • 2





    sudo kill -HUP $(pgrep compiz)

    – isaaclw
    Oct 2 '15 at 21:39






  • 8





    @isaaclw, or pkill -HUP compiz

    – Piotr Findeisen
    Dec 29 '15 at 2:59













  • thanks. It at least I do not need to restart the whole X.

    – Mohamad
    Mar 23 '17 at 8:29

















Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

– dpb
Nov 27 '13 at 16:47







Not sure why this is downvoted. It worked great for me. (even though it reset a lot of window workspaces)

– dpb
Nov 27 '13 at 16:47















This should be the accepted answer.

– jcalfee314
Dec 30 '14 at 18:12





This should be the accepted answer.

– jcalfee314
Dec 30 '14 at 18:12




2




2





sudo kill -HUP $(pgrep compiz)

– isaaclw
Oct 2 '15 at 21:39





sudo kill -HUP $(pgrep compiz)

– isaaclw
Oct 2 '15 at 21:39




8




8





@isaaclw, or pkill -HUP compiz

– Piotr Findeisen
Dec 29 '15 at 2:59







@isaaclw, or pkill -HUP compiz

– Piotr Findeisen
Dec 29 '15 at 2:59















thanks. It at least I do not need to restart the whole X.

– Mohamad
Mar 23 '17 at 8:29





thanks. It at least I do not need to restart the whole X.

– Mohamad
Mar 23 '17 at 8:29











9














I know this is an old post, but Gus's answer helped me and I'd like to add to it. This is what I did (on Ubuntu 12.04):





  • Alt+F2 (run application)

  • Scheduled Tasks

  • New recurrent task

  • killall compiz -HUP

  • Every day at 00:00


Now compiz will be restarted automatically every night, without having to know the process id.



My problem was that if I left my screen locked for a few days, it took ~30 seconds to open the screen lock, and compiz memory usage was around 1000 MB.






share|improve this answer





















  • 1





    On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

    – Luís de Sousa
    Feb 12 '15 at 15:10
















9














I know this is an old post, but Gus's answer helped me and I'd like to add to it. This is what I did (on Ubuntu 12.04):





  • Alt+F2 (run application)

  • Scheduled Tasks

  • New recurrent task

  • killall compiz -HUP

  • Every day at 00:00


Now compiz will be restarted automatically every night, without having to know the process id.



My problem was that if I left my screen locked for a few days, it took ~30 seconds to open the screen lock, and compiz memory usage was around 1000 MB.






share|improve this answer





















  • 1





    On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

    – Luís de Sousa
    Feb 12 '15 at 15:10














9












9








9







I know this is an old post, but Gus's answer helped me and I'd like to add to it. This is what I did (on Ubuntu 12.04):





  • Alt+F2 (run application)

  • Scheduled Tasks

  • New recurrent task

  • killall compiz -HUP

  • Every day at 00:00


Now compiz will be restarted automatically every night, without having to know the process id.



My problem was that if I left my screen locked for a few days, it took ~30 seconds to open the screen lock, and compiz memory usage was around 1000 MB.






share|improve this answer















I know this is an old post, but Gus's answer helped me and I'd like to add to it. This is what I did (on Ubuntu 12.04):





  • Alt+F2 (run application)

  • Scheduled Tasks

  • New recurrent task

  • killall compiz -HUP

  • Every day at 00:00


Now compiz will be restarted automatically every night, without having to know the process id.



My problem was that if I left my screen locked for a few days, it took ~30 seconds to open the screen lock, and compiz memory usage was around 1000 MB.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 1 '14 at 14:10









muru

1




1










answered Dec 1 '14 at 6:39









NorthmoorNorthmoor

9111




9111








  • 1





    On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

    – Luís de Sousa
    Feb 12 '15 at 15:10














  • 1





    On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

    – Luís de Sousa
    Feb 12 '15 at 15:10








1




1





On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

– Luís de Sousa
Feb 12 '15 at 15:10





On Ubuntu 14.04 64bit, compiz gets to 2 Gb of RAM in just 5 or 6 days of continuous activity. This is possibly the best solution given here, and does not bother any of the applications running.

– Luís de Sousa
Feb 12 '15 at 15:10


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f82684%2flowering-compiz-memory-usage%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

張江高科駅