I am getting Windows version of segfault with the latest builds. This is
with glib-2.39.1. Should I file a bugreport or it will sort itself out?
Here is what I see during the crash:
0x6862110F (0x000101ED4790 0x000101ED4780
0x000101ED4790 0x02229D95), g_slice_free1()
This appears to be something new, I would file a bug.
Standard questions:
What was the last version that worked?
What were you doing when it crashed?
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership:
Thanks. I will.
I will also rebuild glib and see if the crash goes away.
In response to your questions.
1. The last version that worked is the one I uploaded to my website.
However, one caveat, I was using it on Windows 7.
2. I was editing a 16-bit tiff and then opening another 16-bit tiff.
36MP.
On Sun, Dec 15, 2013 at 7:47 PM, Liam R E Quin l...@holoweb.net wrote:
On Sun, 2013-12-15 at 18:01 -0500, Partha Bagchi wrote:
I rebuilt glib-2.0 and I am still experiencing crashes. However, it's no
longer the above message. Usually after opening 2 or 3 large 16-bit tiffs
and
On Sun, 2013-12-15 at 18:01 -0500, Partha Bagchi wrote:
I rebuilt glib-2.0 and I am still experiencing crashes. However, it's no
longer the above message. Usually after opening 2 or 3 large 16-bit tiffs
and running unsharp mask and some curves, I get the following with gdb:
How large exactly,
