OS: Windows 7 - (64Bit)
Gimp: 2.8.4 32/64 bit (newest gimp source from git - Parthas version also)

I have a very strange behaviour of gimp.
The reason seems to be libcairo. I compiled the newest 1.12.14 from git and with this version,
1. my pen (only the pen, not the mouse) reacts incredibly (almost unusably) slow.
2. If I use the plugin IWarp and try to move pixels to the upper border of the image, the image gets destroyed. It seems to copy the lower image border to the upper side.
I did heavy testing and it seems to be, no, it IS the libcairo-2.dll, that makes this trouble.
Further testing (compiling my comp to extremly heat) showed, that the last functioning version of libcairo is the 1.11.2.
The version 1.11.4 is completely unfunctionable and from 1.12.0 on the trouble exists.
If someone has this strange behaviour, too, I put the version 1.11.2 as an attachment.

Just replace the version in the gimp\bin directory.

I already made a bug report for cairo. It would be nice, if someone could reproduce the bug.

Hatti

Hatti,

Cairo is broken! Make a lot of noise on their forum that they broke Gimp. Matter of fact Gimp 2.9 will not run on Windows in its current state. See my possible fix at the bug:

https://bugs.freedesktop.org/show_bug.cgi?id=60519

I also talked to Mitch about fixing it, but looks like we have to wait for the Cairo folks to fix it.

Partha

Hi. Yeah, right. They must have changed a lot after 1.11.2. And not all changes are good. The newest version of MyPaint doesn't run on windows, also. Maybe that is also a bug of cairo. Your workaround doesn't fix the described error. I compiled version 1.12.15 (with that fix applied) with the same strange behaviour.

You mean the strange behavior you noted above or that Gimp 2.9 does not boot?

The strange behaviour I noted above.
For compiling 2.9, I used your workaround before. I do not compile 2.9 as often as I compile 2.8.5...