GNOME Bugzilla – Bug 131364
Failed to open a 1800x1200 jpeg
Last modified: 2004-09-13 10:03:33 UTC
When I tried to open a 1800x1200 jpg (taken from an Cannon Digi Camera), gimp failed to open and produce following error message on console: ====== console log ===== jpeg in malloc(): warning: recursive call jpeg in malloc(): warning: recursive call (process:10126): GLib-ERROR (recursed) **: gmem.c:140:g_malloc(): failed to allocate 52 bytes aborting... (gimp-1.3:10124): LibGimpBase-WARNING **: gimp-1.3: wire_read(): error (gimp-1.3:10124): Gimp-Plug-In-WARNING **: plug_in_close: plug-in aborted before sending its procedure return values ==== end of console log ==== gimp version is GIMP version 2.0pre1, and I saw it in 1.3.29 before I upgraded gimp to 2.0pre1. This picture file was taken by a digital camera. ImageMagic or eog or xv open it without problems. But for this paticular image, even after I rendered (blur) and resave it, gimp still cannot open it. If you want the image, I can send it to you. Regards
Created attachment 23321 [details] failed to open jpg file (rendered for privacy).
This JPEG and other images I tried open w/o any problems here. I am using libjpeg62-6b (taken from the debian package name) on i686 GNU/Linux. This looks like an issue with libjpeg. Can you please try if other applications that use the same version of libjpeg also show problems to load this image? What hardware platform are you running gimp on? Is there a chance you could run a debugger on the jpeg plug-in?
I checked my jpeg lib, it is (from freebsd port output) jpeg-6b_1 IJG's jpeg compression utilities This lib is used as well by other utilities such as eog and there is no problem. The hardware is an IBM T30 laptop. I don't know how to run a debugger on the libjpeg.so.6, would you tell me how to do that? Thanks
Looks like we are using the same version of libjpeg on very similar hardware (this being an IBM T23). The basic procedure on how to debug GIMP plug-ins using gdb is described in devel-docs/debug-plug-ins.txt as found in the GIMP source tree. This document assumes you know how to use gdb to attach to a running process and how to obtain useful information such as a backtrace. In case you need help with that, let us know.
This bug report is awaiting feedback from the reporter.
My guess is that this is just a duplicate of bug #142252. Closing as duplicate.
*** This bug has been marked as a duplicate of 142252 ***