Re: [Gimp-developer] Scripting: creating a channel from a layer in another image and other channel-related manoeuvres
When in doubt, gimp-edit-copy and gimp-edit-paste can be quite handy to transfer pixels across layers/channels/images. On 14 December 2013 11:49, Ofnuts wrote: > On 12/14/2013 12:21 AM, Ofnuts wrote: >> >> Then, gimp-layer-create-mask will accept a ADD-CHANNEL-MASK (6) type, but >> in this case how do I specify the channel? > > > Some googling got me an answer to this (it uses the active channel) so I > have that part covered. Now for the other question, any takers? > > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://gnome.org/archives/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
[Gimp-developer] New gitsource build segfault (Windows 8.1)
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() + 0x17F bytes(s) 0x02248B1D (0x3F847AE147AE147B 0x0036 0x841EBF40 0x841EBF40), g_type_free_instance() + 0x18D bytes(s) 0x6207F64A (0x0002 0x136F3500 0x136F3500 0x13534B00), gegl_tile_cache_destroy() + 0x2EA bytes(s) 0x0222A345 (0x 0x685D86BD 0x 0x), g_object_unref() + 0x115 bytes(s) 0x6207E138 (0x 0x137A0670 0x620956F0 0x841EB5B0), gegl_tile_backend_swap_cleanup() + 0x468 bytes(s) 0x0222A345 (0x2181A740 0x2181A740 0x3C8BD210 0x8420FDE0), g_object_unref() + 0x115 bytes(s) 0x0224D027 (0x817AD9E0 0x2181A740 0x841EB5B0 0x), g_value_unset() + 0x27 bytes(s) 0x62089C22 (0x0023F8C0 0x10FD1340 0x899005D0 0x0023F8B0), gegl_operation_context_purge() + 0x32 bytes(s) 0x62095CC2 (0x0002 0x02249ABE 0x0001 0x007F3932), gegl_graph_process() + 0x82 bytes(s) 0x620953A1 (0x0100 0x007F3A6E 0x0001 0x137C26D0), gegl_eval_manager_apply() + 0x111 bytes(s) 0x6208CC75 (0x0001 0x686212CC 0x 0x685F5AE0), gegl_node_blit_buffer() + 0x45 bytes(s) 0x00753840 (0x 0x7FFF 0x0023FC00 0x033DB890) 0x685FB665 (0x 0x6862BE90 0x03431420 0x033DB890), g_main_context_dispatch() + 0x135 bytes(s) 0x685FB998 (0x 0x006B003D 0x 0x), g_main_context_dispatch() + 0x468 bytes(s) 0x685FBE27 (0x034763A0 0x 0x00A40830 0x00409F80), g_main_loop_run() + 0x67 bytes(s) 0x0040182B (0x0001 0x002B 0x00A40830 0x00A4C960) 0x0080CF12 (0x0001 0x00A4C960 0x 0x) 0x004013D5 (0x 0x 0x 0x) 0x004014D8 (0x 0x 0x 0x) 0x7FFF9FBC15CD (0x 0x 0x 0x), BaseThreadInitThunk() + 0xD bytes(s) 0x7FFFA00343D1 (0x 0x 0x 0x), RtlUserThreadStart() + 0x1D bytes(s) ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] New gitsource build segfault (Windows 8.1)
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: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] New gitsource build segfault (Windows 8.1)
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. On Sun, Dec 15, 2013 at 1:25 PM, Daniel Sabo wrote: > 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: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] New gitsource build segfault (Windows 8.1)
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: warning: HEAP[gimp-2.9.exe]: warning: HEAP: Free Heap block 82DCA470 modified at 82DE3850 after it was freed Program received signal SIGTRAP, Trace/breakpoint trap. 0x7fffa00b55f6 in ?? () (gdb) bt #0 0x7fffa00b55f6 in ?? () #1 0x7fffa000503c in ?? () #2 0x7fffa0061dc0 in ?? () #3 0x82dca470 in ?? () #4 0x82de3850 in ?? () #5 0x003902c0 in ?? () #6 0x007f in ?? () #7 0x8a0085c0 in ?? () #8 0x5100 in ?? () #9 0x in ?? () So, can't reproduce the prior error, but it's something else now. Thanks, Partha On Sun, Dec 15, 2013 at 4:34 PM, Partha Bagchi wrote: > 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. > > > > On Sun, Dec 15, 2013 at 1:25 PM, Daniel Sabo wrote: > >> 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: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] New gitsource build segfault (Windows 8.1)
36MP. On Sun, Dec 15, 2013 at 7:47 PM, Liam R E Quin 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 running unsharp mask and some curves, I get the following with gdb: > > How large exactly, in pixels? 64-bit gimp? > > I was having problems recently feathering the selection that related to > an integer overflow in the size of a gegl buffer. Not saying you have > the same problem of course, but that the dimensions of the image may > matter. > > Liam > > -- > Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ > Pictures from old books: http://fromoldbooks.org/ > Ankh: irc.sorcery.net irc.gnome.org freenode/#xml > > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] New gitsource build segfault (Windows 8.1)
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, in pixels? 64-bit gimp? I was having problems recently feathering the selection that related to an integer overflow in the size of a gegl buffer. Not saying you have the same problem of course, but that the dimensions of the image may matter. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://gnome.org/archives/gimp-developer-list
