Unminimized xchat window consistently causes high compiz cpu usage and poor compiz performance

[Carey Underwood]

Binary package hint: xchat

I'm on a fairly slow machine, but it's generally perfectly snappy.

Experienced with nouveau from edgers and with restricted nvidia driver.

With xchat open but minimized, idle compiz cpu usage is around 2% to 5%.
With xchat restored, with an idle channel visible, compiz cpu usage goes to 40%, and other desktop operations (dragging windows, working in other applications) becomes noticeably jittery / laggy.
Minimizing xchat again brings compiz cpu usage back down to idle.

This occurs on a freshly restarted compiz and xchat process. (via closing and quiting xchat and "compiz --replace")

Running
> strace -p $(pidof compiz) -o /tmp/strace-compiz-$MODE & strace -p $(pidof xchat) -o /tmp/strace-xchat-$MODE & sleep 2s; kill %1; kill %2
with xchat minimized and visible (the output of which is attached) shows both compiz and xchat with an order of magnitude more activity while visible (again with only an idle channel visible).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xchat 2.8.6-4ubuntu5
Uname: Linux 2.6.34-020634-generic i686
Architecture: i386
Date: Sat Jun 26 02:13:49 2010
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: xchat

[Carey Underwood (cwillu)]

strace-xchat-restored: 686K
strace-compiz-restored: 371K
strace-xchat-minimized: 45K
strace-compiz-minimized: 99K

[Carey Underwood (cwillu)]

It appears to be the graphical lag meter; if I set view | Network Meters to "Graph" or "Both", I get the excessive cpu usage. If I set them instead to "Text" or "None", I get the same cpu usage as a minimized xchat.

[Braiam Peguero (braiampe)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Carey Underwood (cwillu)]

It's still broken in the latest.