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 631766 - Bad performance when moving brush outline on canvas
Bad performance when moving brush outline on canvas
Status: RESOLVED DUPLICATE of bug 304798
Product: GIMP
Classification: Other
Component: Tools
git master
Other All
: Normal normal
: 2.8
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-10-09 15:55 UTC by Martin Nordholts
Modified: 2011-03-18 10:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin Nordholts 2010-10-09 15:55:43 UTC 
Step-by-step:
1. rm -r ~/.gimp-2.7 and start GIMP
2. Create a new image of default size
3. Move the brush outline on the canvas

Expected result:
Very mild CPU usage

Actual result:
Very high CPU usage

The reason is of course that we use cairo to draw the outline now, we didn't have this problem with XOR. We need to mitigate the CPU usage somehow.
Comment 1 Michael Natterer 2010-10-09 19:14:36 UTC 
The problem is  also that I removed the draw timeout which prevented
too many redraws per second. Let's revisit this when the brush outline
is actually drawn correctly.
Comment 2 Michael Natterer 2010-10-10 10:07:49 UTC 
Now that the brush outline works again, I'd still like to benchmark things
first before hiding slowness away by re-introducing the timeout.
Comment 3 Michael Natterer 2011-03-18 10:52:47 UTC 
The timeout is there again, so things are much better now. However, only
the über-slowness is fixed and it's still worse than with XOR.

Resolving as duplicate because we don't need teo brush outline slowness
bugs open.

*** This bug has been marked as a duplicate of bug 304798 ***