strong visual tearing / rendering glitches while moving objects

Bug #1510704 reported by Lukas F. Hartmann
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

Whenever I move an object -- simple or complex doesn't matter -- the object is redrawn in visually overlapping discontinous bands that make the correct placing of objects very hard.

Changing rendering options (threads or memory) doesn't seem to have an impact.


Non-moving object:
Object while moved:

Inkscape 0.91 r13725
Debian 8
Linux irata-debian 4.1.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 4.1.3-1~bpo8+1 (2015-08-12) x86_64 GNU/Linux

Hardware is 13" Retina Macbook Pro 2013

Desktop Environment xfce4

Revision history for this message
Lukas F. Hartmann (luzas) wrote :
su_v (suv-lp)
tags: added: performance renderer-cairo
Revision history for this message
Lukas F. Hartmann (luzas) wrote :

Here is my "test case" as per request

Revision history for this message
su_v (suv-lp) wrote :

Reproduced on OS X 10.7.5 (GTK+/X11) with Inkscape 0.91 r13725, 0.91+devel r14430 (tested with cairo 1.14.2 and cairo git master).

- turning off caching does have no effect;
- the rendering glitches don't reproduce if zooming out further;
- removing the stroke (or converting it to path) does reduce the rendering glitches.

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
trlkly (trlkly) wrote :

I can confirm this bug on Windows 7 as well. It's worst in the 32-bit version, but it also shows up in the 64-bit version. It's actually best in an old 0.91 beta I still happened to have, but it still happens.

I note that GIMP had this same problem in 2.8. I believe it was fixed in 2.8.4. I don't think it's purely a performance issue, even if it is only noticeable with larger amounts of data. It seems to me more like it's painting in the wrong order.

It sucks, because 0.91 has a few nifty features, but it's unusable in this state. Seems strange to me that it had such a long beta and this wasn't caught.

Revision history for this message
Mc (mc...) wrote :

Tackled by psychon in commit 8825db4e6132bada6cd86b93e6591aa3a53e86b7

Changed in inkscape:
status: Confirmed → Fix Committed
milestone: none → 0.93
su_v (suv-lp)
tags: added: backport-proposed
Revision history for this message
Patrick Storz (ede123) wrote :
tags: removed: backport-proposed
Changed in inkscape:
milestone: 0.93 → 0.92.2
assignee: nobody → Max Gaukler (mgmax)
Max Gaukler (mgmax)
Changed in inkscape:
assignee: Max Gaukler (mgmax) → nobody
Revision history for this message
Patrick Storz (ede123) wrote :

Sorry, wrong commit... (gnore comment #6)

Backported to 0.92.x in

Revision history for this message
Patrick Storz (ede123) wrote :

I'm really goo ad copy pasting wrong links apparently.

Commit in ä#7 was the original commit to master, the commit in 0.92.x is

(If I still got it wrong please fix it since I'm apparently incapable of getting this right ;-) )

jazzynico (jazzynico)
Changed in inkscape:
status: Fix Committed → Fix Released
Revision history for this message
MM (mm90) wrote :

I'm using Windows 7 64-bit and Inkscape 92.4 and I'm still having this issue. I tested with two graphic boards (AMD and Nvidia), both up-to-date and it happens on both of them. It doesn't matter if the object is a simple path or a group with several other objects, it happens the same way. The only "temporary" fix is zooming in and out every time it shows up.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers