Excessive CPU load in settings window

Bug #108650 reported by Lars Ljung
6
Affects Status Importance Assigned to Milestone
xchat-gnome (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xchat-gnome

When the settings dialog window is open xchat-gnome and Xorg is using about 40% CPU each. When I close the settings window everything goes back to normal. It's not crashing.

When using strace I get this when opening the settings window (most of it cut out):
...
gettimeofday({1177182122, 29990}, NULL) = 0
gettimeofday({1177182122, 30250}, NULL) = 0
gettimeofday({1177182122, 36013}, NULL) = 0
gettimeofday({1177182122, 36307}, NULL) = 0
gettimeofday({1177182122, 40308}, NULL) = 0
gettimeofday({1177182122, 40624}, NULL) = 0
gettimeofday({1177182122, 51438}, NULL) = 0
gettimeofday({1177182122, 52272}, NULL) = 0
gettimeofday({1177182122, 52357}, NULL) = 0
gettimeofday({1177182122, 52728}, NULL) = 0
gettimeofday({1177182122, 52854}, NULL) = 0
gettimeofday({1177182122, 52912}, NULL) = 0
gettimeofday({1177182122, 58051}, NULL) = 0
gettimeofday({1177182122, 58362}, NULL) = 0
gettimeofday({1177182122, 63228}, NULL) = 0
gettimeofday({1177182122, 64073}, NULL) = 0
gettimeofday({1177182122, 68723}, NULL) = 0
gettimeofday({1177182122, 68830}, NULL) = 0
gettimeofday({1177182122, 68911}, NULL) = 0
gettimeofday({1177182122, 69198}, NULL) = 0
gettimeofday({1177182122, 69501}, NULL) = 0
gettimeofday({1177182122, 69754}, NULL) = 0
gettimeofday({1177182122, 70024}, NULL) = 0
gettimeofday({1177182122, 70065}, NULL) = 0
gettimeofday({1177182122, 73791}, NULL) = 0
gettimeofday({1177182122, 74068}, NULL) = 0
gettimeofday({1177182122, 77496}, NULL) = 0
gettimeofday({1177182122, 77783}, NULL) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
Process 12214 detached

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

Which versions of Ubuntu and Xchat are you using?

Revision history for this message
Lars Ljung (larslj) wrote :

Sorry, Feisty and xchat-gnome 0.16-ubuntu3.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in xchat-gnome:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Lars Ljung (larslj) wrote :

No backtrace available since the program doesn't actually crash (except when using strace, but forget about that)

I cleared all gconf settings for xchat-gnome and the problem disappeared. But when I set a background image the problem returns, even if I disable the use of the background image. This is reproducible on my system.

Once you have tried to use a background image there is only one way to solve the problem, that is to clear the value of /apps/xchat/main_window/background_image using gconf-editor. When you clear the value the CPU usage immediately drops. I tried it with png and gif images, not sure if it matters though.

Changed in xchat-gnome:
status: Needs Info → Unconfirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Is this still an issue for you? May you please try to reproduce it with Gutsy? you can grab a CD Image from here: http://www.ubuntu.com/testing/ thanks in advance.

Changed in xchat-gnome:
status: New → Incomplete
Revision history for this message
Lars Ljung (larslj) wrote :

Just tried it on Gutsy and I can't reproduce it there, so I guess you can close this bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the bug then, feel free to reopen if you get the issue again with the new version though

Changed in xchat-gnome:
status: Incomplete → Fix Released
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

I reopen this bug since I get the preferences window eats 100% of my CPU.
I'm using Ubuntu Hardy with xchat-gnome version 1:0.18-2ubuntu1.

Changed in xchat-gnome:
status: Fix Released → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen issues closed for months only because you have a similar bug, open a new one rather

Changed in xchat-gnome:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.