← Back to team overview

desktop-packages team mailing list archive

[Bug 861408] Re: Metacity hangs and consumes 100% CPU

 

** Description changed:

  I'm using ubuntu 11.04 i386 with proprietary nVidia drivers.
  metacity package has version 2.30.3-0ubuntu8
  Compositing is disabled.
  
- Sometimes (~once a week) metacity stops responding and starts consuming 100% CPU. Usually it happens when I close a window. After it all windows become unusable.
- Running metacity-message restart has no effect. If I kill metacity process the whole X-session terminates and gdm appears.
+ Sometimes (~once a week) metacity stops responding and starts consuming 100% CPU. Usually it happens when I close a window. After that all windows become unusable.
+ Running something like
+ DISPLAY=:0 metacity-message restart
+ from console seems to have no effect. Then I kill metacity process (only SIGKILL works) and the whole X-session terminates and gdm appears.
  
  Update:
  I noticed, that last time I met this bug my ~/.xsession-errors was flooded up to size of 2GiB with following two messages:
  (metacity:2769): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed
  (metacity:2769): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 27:File too large

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/861408

Title:
  Metacity hangs and consumes 100% CPU

Status in “metacity” package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 11.04 i386 with proprietary nVidia drivers.
  metacity package has version 2.30.3-0ubuntu8
  Compositing is disabled.

  Sometimes (~once a week) metacity stops responding and starts consuming 100% CPU. Usually it happens when I close a window. After that all windows become unusable.
  Running something like
  DISPLAY=:0 metacity-message restart
  from console seems to have no effect. Then I kill metacity process (only SIGKILL works) and the whole X-session terminates and gdm appears.

  Update:
  I noticed, that last time I met this bug my ~/.xsession-errors was flooded up to size of 2GiB with following two messages:
  (metacity:2769): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed
  (metacity:2769): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 27:File too large

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/861408/+subscriptions


References