Your message dated Thu, 28 Aug 2014 23:19:25 +0000
with message-id <[email protected]>
and subject line Fwd: Re: [wmbubble] 10x increase in CPU usage (Debian bug
#609859) (#7)
has caused the Debian Bug report #609859,
regarding wmbubble: 10x increase in CPU usage
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
609859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609859
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wmbubble
Version: 1.46-2.1
Severity: normal
In lenny, wmbubble used to have neglible CPU usage even on very moderate
machines. With squeeze, it uses about 2% CPU (according to top) on a 1 GHz
Pentium III.
Profiling shows that more than 90% of the CPU time is spent below the "Drawing
magic" comment in bubblemon_update, and more than 80% in the copying loop into
bm.rgb_buf that takes about 100 us a pop.
This is on a 24-bit visual --
according to xdpyinfo
default visual id: 0x21
visual:
visual id: 0x21
class: TrueColor
depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff0000, 0xff00, 0xff
significant bits in color specification: 8 bits
--, and given that all I can see is that wmbubble uses gdk_visual_get_system,
I'm hoping someone else sees why something appears to see some need for costly
pixel translation operations here.
Possibly related (I've not really tried to understand this), wmbubble emits a
warning when it creates the icon window:
(wmbubble:17924): Gdk-WARNING **: /build/buildd-
gtk+2.0_2.20.1-2-i386-TNeM25/gtk+2.0-2.20.1/gdk/gdkwindow.c:1396Toplevel
windows must be created as children of
of a window of type GDK_WINDOW_ROOT or GDK_WINDOW_FOREIGN
-- System Information:
Debian Release: 6.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.35.10
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to
de_DE)
Shell: /bin/sh linked to /bin/bash
Versions of packages wmbubble depends on:
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra
ii libfontconfig1 2.8.0-2.1 generic font configuration library
ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface
ii libpango1.0-0 1.28.3-1 Layout and rendering of internatio
ii libx11-6 2:1.3.3-4 X11 client-side library
wmbubble recommends no packages.
Versions of packages wmbubble suggests:
ii aterm [x-terminal-emulator] 1.0.1-7+b1 Afterstep XVT - a VT102 emulator f
ii konsole [x-terminal-emulator] 4:4.4.5-1 X terminal emulator
ii rxvt-unicode [x-terminal-emul 9.07-2+b1 RXVT-like terminal emulator with U
ii sox 14.3.1-1 Swiss army knife of sound processi
ii xterm [x-terminal-emulator] 261-1 X terminal emulator
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.50
-------- Forwarded Message --------
Subject: Re: [wmbubble] 10x increase in CPU usage (Debian bug #609859)
(#7)
Date: Thu, 28 Aug 2014 15:50:01 -0700
From: Robert Jacobs
<[email protected]><mailto:[email protected]>
Reply-To: rnjacobs/wmbubble
<reply+i-39362975-87a64c2acb54bb1f7027bf05ad3b1e9ab4543934-1992...@reply.github.com><mailto:reply+i-39362975-87a64c2acb54bb1f7027bf05ad3b1e9ab4543934-1992...@reply.github.com>
To: rnjacobs/wmbubble
<[email protected]><mailto:[email protected]>
CC: Doug Torrance
<[email protected]><mailto:[email protected]>
Debian 609859 was filed against 1.46 and years after its release, so that
really sounds like it was exposing a bug in GDK.
Anyway, 1.46→1.50 ripped out the corresponding GDK code and replaced it with
XImage calls, so I think you can close that one.
---
Reply to this email directly or view it on GitHub:
https://github.com/rnjacobs/wmbubble/issues/7#issuecomment-53815956
--- End Message ---
