I seem to get tiff errors when I am loading a 16-bit tiff say after opening a couple of images of other formats like png or jpeg. Other times if I open the tiff first, it seems to open fine.

I am stumped. :(

The error is :LibGimp-WARNING (recursed) **: file-tiff-load.exe: gimp_flush(): error: Invalid argument

Gimp then crashes, that is closes completely. I can provide the Windows crash message, but I doubt that it will be helpful.

Gimp git updated today on Window 7 64-bit.

Thanks, Partha

Hi Cristian,

Thanks for the feedback. Now we are getting somewhere. :)

I use libtiff 4.0.2. I wonder which version Ender is using. I will see whether upgrading to 4.0.3 (the latest stable release) makes any difference.

Note that gimp-2.9 crashes I am talking about usually happens when you try to open a 16-bit TIFF. Unfortunately, the crashes are random in the sense that same file in a new Gimp session will open fine while in another session with multiple files (> 1) open, it will sometimes crash without leaving a trace. So not much information to provide.

I am guessing this is a memory management issue which is different on Windows than on Linux/Mac.

Partha

On Sun, Apr 21, 2013 at 3:53 AM, Cristian Secară wrote:

În data de Sun, 21 Apr 2013 10:40:05 +0300, Cristian Secară a scris:

If I use your portable Windows version (gimp-2.8.4, probably a February build), load any image (even a 1x1 pixel.gif) and then load this image http://www.secarica.ro/temp/grading_test_v03.tif a dialog tells me "Unknown field with tag 37724 (0x935c) encountered".

Some more info: it has something to do with the particular area where I drop the file.

I mean: with GIMP (your version) either fresh opened or all previous images closed, if I drag and drop my test image over the design area, the image opens just fine.

If I drag and drop my test image over the toolbox, even the first time, the mentioned error shows up.

Because in case of an already opened image, for the second (third, etc.) I always drag and drop over the toolbox area (instead of the design area), this was the reason for "erorr occurs only with another image already there".

I never use the open dialog, so I cannot tell what happens then.

Cristi

-- Cristian Secară
http://www.secarica.ro
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Christian,

Does the official version you have include ufraw-gimp? If not, can you move ufraw-gimp out of the plug-ins folder and retry the tiff file and let me know if you have issues.

The ufraw plugin tries to do the following:

/* if UFRaw fails on jpg/jpeg or tif/tiff then open with GIMP */ if (uf == NULL) {
if (!strcasecmp(filename + strlen(filename) - 4, ".jpg") || !strcasecmp(filename + strlen(filename) - 5, ".jpeg")) { if (loadThumbnail)
*return_vals = gimp_run_procedure2("file_jpeg_load_thumb", nreturn_vals, nparams, param);
else
*return_vals = gimp_run_procedure2("file_jpeg_load", nreturn_vals, nparams, param);
gdk_threads_leave();
return;
} else if (!strcasecmp(filename + strlen(filename) - 4, ".tif") || !strcasecmp(filename + strlen(filename) - 5, ".tiff")) { if (!loadThumbnail)
*return_vals = gimp_run_procedure2("file_tiff_load", nreturn_vals, nparams, param);
else {
/* There is no "file_tiff_load_thumb". * The call to "file_ufraw_load" will handle the thumbnail */ /* Following is another solution for tiff thumbnails GimpParam tiffParam[3]; tiffParam[0].type = GIMP_PDB_INT32; tiffParam[0].data.d_int32 = GIMP_RUN_NONINTERACTIVE; tiffParam[1].type = GIMP_PDB_STRING; tiffParam[1].data.d_string = filename; tiffParam[2].type = GIMP_PDB_STRING; tiffParam[2].data.d_string = filename; *return_vals = gimp_run_procedure2 ("file_tiff_load", nreturn_vals, 3, tiffParam); */
}
gdk_threads_leave();
return;
} else {
......

BTW, when I started this thread, I explicitly stated that I was reporting the issue with gimp from git. I guess I should have mentioned that it was the master branch (2.9.1). :(

Thanks, Partha

On Sun, Apr 21, 2013 at 12:06 PM, Cristian Secară wrote:

În data de Sun, 21 Apr 2013 08:10:31 -0400, Partha Bagchi a scris:

Note that gimp-2.9 crashes I am talking about usually happens when you try to open a 16-bit TIFF.

Hmm ...
I loaded at random a 16 bit tiff image.

Case A - your 2.8.4 portable version, drop the tiff file over the design area:
- a GIMP Message box tells me that my file is unsupported file format - if I just click OK, the popup box close and nothing else happens - if I try to move that box with the mouse, then a Windows error box (title bar: Microsoft Visual C++ Runtime Library) tells me that "This application has requested the Runtime to terminate it in an unusual way, blah, blah."; another Windows error box tells me that ufraw-gimp.exe no longer works
- after closing the last Windows error box, a single GIMP Message error box tells me that (1) the plugin ufraw-gimp.exe has crashed / GIMP restart is recommended and (2) opening of my image has failed - GIMP remains open, with blank drawing space

If I drop the tiff file over the toolbox area, the single difference is that the last (1) and (2) GIMP error messages are shown each in separate error boxes.

Case B - the official 2.8.4 installed version, either drop method: - a GIMP Message tells me this sting "Warning:\n The image you are loading has 16 bits per channel. GIMP can only handle 8 bit, so it will be converted for you. Information will be lost" - GIMP remains open, with the desired image on it, reduced to 8 bit; I can continue to work on it, if so desired

Cristi

-- Cristian Secară
http://www.secarica.ro
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

Christian,

Absolutely. Don't get me wrong. :)

I was simply pointing out that Gimp git was what I was referring to in my original post.

In terms of your compiling, if you are interested, I will be happy to make Gimp 2.9.x available to you for testing purposes. Let me know which flavor you like - Windows 32bit, 64bit or Mac (Snow Leopard or Higher).

Thanks again, Partha

On Sun, Apr 21, 2013 at 2:43 PM, Cristian Secară wrote:

În data de Sun, 21 Apr 2013 14:12:12 -0400, Partha Bagchi a scris:

Does the official version you have include ufraw-gimp?

No.

If not, can you move ufraw-gimp out of the plug-ins folder and retry the tiff file and let me know if you have issues.

I copied the required files and yes, now the official version behaves exactly the same as yours.

I copied the ufraw-gimp.exe file, which then requested the pthreadGC2-W64.dll and libgtkimageview-0.dll additional files.

BTW, when I started this thread, I explicitly stated that I was reporting the issue with gimp from git. I guess I should have mentioned that it was the master branch (2.9.1). :(

Yes, but I cannot check (compile) anything for myself and I hoped that my tiny investigation can maybe help somehow to narrow the issue ...

Cristi

-- Cristian Secară
http://www.secarica.ro
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list