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 631203 - Scrolling in GtkTextView can use 100% cpu
Scrolling in GtkTextView can use 100% cpu
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkTextView
2.91.x
Other All
: Normal major
: 3.0
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-10-03 01:30 UTC by José Aliste
Modified: 2010-10-03 10:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch fixing the issue (1.18 KB, patch)
2010-10-03 03:42 UTC, José Aliste 		none Details | Review

Description José Aliste 2010-10-03 01:30:52 UTC 
Some of us have noticed some slowness and 100% cpu usage on GtkSourcView current gtk master branch. I actually tested the scrolling with the TextView demo on gtk-demo and found the bug is actually on TextView and not on GtkSourceView. Happily, this allowed me to do git bisect on gtk and find  that commit 331999 seems to be the responsible for the perf regression.
Comment 1 José Aliste 2010-10-03 03:42:27 UTC 
Created attachment 171612 [details] [review]
patch fixing the issue

It turns out it was a missuse of cairo_clip_extents. The attached patch fixes the issue. Please review.
Comment 2 Benjamin Otte (Company) 2010-10-03 10:35:12 UTC 
commit 846f774642c06c88358ef3c4c8174d180caf1be2
Author: José Aliste <jaliste@src.gnome.org>
Date:   Sun Oct 3 12:14:48 2010 +0200

    textview: Fix clip usage
    
    The previous code used cairo_clip_extents() and interpreted its
    parameters wrong.