Comment 61 for bug 825709

The high cpu usage is independent of position_fix=1. It looks like a problem related to the interface, which for some reason is slow in handling mouse events in submenus of Applications and in the Places menu, to some extent also in file context menus and in Nautilus menus.

On the other hand I am experiencing too much randomness for reliable testing, because at random banshee does not handle well changes in its window. Examples:
- if I resize the lower right view (Name Artist etc.)
  - it randomly locks X (cpu at 100%)
  - the sound is corrupted, until playback is stopped and restarted (this case occured with pulseaudio running)
- on startup while recording the log as recommended
  - refuses to show the contents of its window (cpu at 95% in the Resources window)
  - shows the window and then crashes with a GLib-CRITICAL failed assertion

I wonder if it would not be safer to update all the packages except pulseaudio and see if independent problems have been solved.

To summarize the current state

- no pulseaudio: OK
- pulseaudio & no fix: choppy sound, but not always
- pulseaudio & position_fix=1: OK, sound silenced for one second or less if one rearranges windows etc.

Surely, position_fix=1 is a substantial improvement. But as I said I would be very interested in continuing to test it with updated packages.