After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 313015 - libsexy + gtk 2.8 causes 100% CPU load from X
libsexy + gtk 2.8 causes 100% CPU load from X
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: High critical
: ---
Assigned To: pango-maint
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-08-09 15:26 UTC by Luis Villa
Modified: 2005-08-24 20:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luis Villa 2005-08-09 15:26:32 UTC 
So, compile everything with teh sexy, and after entering characters in the main
text entry field, X goes all to hell. (This is a very new X from ubuntu, CVS
gtk, new-ish everything.) Nuke libsexy and rebuild and things are fine again. I
doubt it is an xchat-gnome bug per se, but that is what is revealing it so I
figured this was the least bad place to start.
Comment 1 Luis Villa 2005-08-21 19:32:42 UTC 
After some conversation in IRC, this definitely looks like a libsexy/gtk2.8
thing- libsexy against 2.6 seems to work for everyone in IRC, and everyone with
the problem is running 2.8.
Comment 2 Luis Villa 2005-08-22 03:17:01 UTC 
This can be duplicated by checking out libsexy[1], building it, and running
tests/test-spell-entry. Given that the duplication case is easier than I
thought, and that this happens only with gtk 2.8 and not 2.6, reassigning to gtk.

[1]svn co http://osiris.chipx86.com/svn/osiris-misc/trunk/libsexy/
Comment 3 Matthias Clasen 2005-08-22 15:23:20 UTC 
Can you provide a stacktrace from when X goes to hell ?
Comment 4 Luis Villa 2005-08-22 16:30:05 UTC 



+
Trace
    62589






    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
poll

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#2
g_main_context_iterate

    
                at gmain.c
                  line
                  2867

    

    • 

  • 
#3
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2769

    

    • 

  • 
#4
IA__gtk_main

    
                at gtkmain.c
                  line
                  974

    

    • 

  • 
#5
main

    
                at test-spell-entry.c
                  line
                  35

    

    • 








Not very exciting; I have the feeling I'm doing something wrong, but...






Comment 5


Matthias Clasen





          2005-08-22 17:48:24 UTC
        



Looks like a problem with PANGO_ERROR_UNDERLINE.
If I comment out the setting of that attribute in sexy-spell-entry.c,
things return to normal.






Comment 6


Matthias Clasen





          2005-08-22 19:30:33 UTC
        



Seems to be a problem with the implementation of squiggly underlines in 
PangoCairoRenderer. They work fine in GtkTextView and GtkLabel, which use
GdkPangoRenderer. Curiously, the two implementations are almost the same,
modulo some y axis flipping. 







Comment 7


Owen Taylor





          2005-08-24 20:04:38 UTC
        



Underline was being rendered 1024 times too big in both directions.

2005-08-24  Owen Taylor  <otaylor@redhat.com>

        * pango/pangocairo-render.c (draw_error_underline): convert
        from Pango units to doubles, fix some coordinate space problems
        that had previously been fixed in GTK+. (#313015, Luis Villa)