Results 1 to 9 of 9

Thread: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

  1. #1
    Join Date
    May 2010
    Beans
    4

    Question After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    Hello,

    I have 10.04 installed on my Laptop (Dell Latitude D630 with the Nvidia video upgrade). This was a clean install to a hard drive that I let it totally erase and use as it saw fit. I am using the Nvidia driver marked as "current" in the hardware driver settings.

    When my laptop screen dims due to inactivity, such as not used for 5 mins or so, it will prompt me for a password to log back in. No big deal. However, when it resumes from this state it is SLOW!! I go to system monitor and see that the process "Compiz" is burning up both of my cores at about 70% or HIGHER. It's not using a significant amount of memory which is strange.

    From what I have been able to gather Compiz has some responsibilty for the GUI and killing the process to attempt to restart it is a "bad idea" (tried that lol).

    This also occurs when the laptop hibernates.

    I see that there are various posts referencing hibernate/suspend issues but, I am still getting my feet wet with some of the terminology here so some of them hurt my brain. Any help would be appreciated.

    Thanks,
    iGmO

  2. #2
    Join Date
    May 2010
    Beans
    4

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    I will actually add that Compiz will continue to eat up processor until I reboot the machine. This of course annihilates battery life and generates a lot of heat.

    Is there anyway to reset compiz without a reboot? A script or something I can use after I come from suspend/hibernate?

    Thanks,
    igmo

  3. #3
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 22.04 Jammy Jellyfish

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    Code:
    metacity --replace
    in the run dialog (Alt+F2) will stop compiz and start metacity and you can then use
    Code:
    compiz --replace
    to start compiz again.

    The easiest way though is to get compiz-switch from Forlong and use that. All it needs is a single click to turn compiz on and off.

  4. #4
    Join Date
    May 2010
    Beans
    4

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    Thanks I'll give that a shot!

  5. #5
    Join Date
    May 2010
    Beans
    4

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    Thanks a bunch, using that program to switch off compiz and then back on immediately does the trick!

    You da man.

    iGmO

  6. #6
    Join Date
    Jun 2010
    Beans
    1

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    This looks like a bug in compiz. I experience the same symptoms on a desktop amd64 with geforce 7050: after longer suspend (few hours) it eats about 80% of CPU. Lucid, fresh install. Disabling compiz helps.

  7. #7
    Join Date
    Jul 2009
    Beans
    23

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    0janek: this happens to me too. It only seems to happen after long suspends. I am using nvidia drivers on Lucid, and didn't have a similar problem under Jaunty. Restarting compiz doesn't help; neither does restarting X entirely: I have to reboot the whole system. Does that correspond with your experience? Is there a launchpad bug for this?

  8. #8
    Join Date
    May 2011
    Beans
    13

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    It's been a while since the last post on this thread but i am having the same problem with 11.04. did anyone ever find out the cause of this. compiz-switch doesn't work in natty.

  9. #9
    Join Date
    Oct 2011
    Beans
    1

    Re: After Suspend or Hibernate Compiz Process is using 75%+ procsessor

    waiting patiently for anyone to answer the thread. I am going to have to write something to auto kill it from cron I guess.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •