After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686292 - JPEG import filter: GIMP crashes upon opening a JPEG file
JPEG import filter: GIMP crashes upon opening a JPEG file
Status: RESOLVED DUPLICATE of bug 682454
Product: GIMP
Classification: Other
Component: General
2.8.2
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-10-17 12:24 UTC by gnome-bugzilla
Modified: 2012-10-31 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description gnome-bugzilla 2012-10-17 12:24:59 UTC
Executive summary: 
GIMP crashes when trying to open the JPEG file located at http://www.amateurphotographer.co.uk/imageBank/f/Fisheye%206mm2.8%20001.low.jpg .

Platform details: 
GIMP 2.8.2 (current stable build from http://gimp-win.sourceforge.net/stable.html ) running on Windows Vista SP1.

Steps to reproduce:
1. Download image from http://www.amateurphotographer.co.uk/imageBank/f/Fisheye%206mm2.8%20001.low.jpg .
2. Open the file in GIMP.

Expected result:
File opened normally, ready for editing.

Actual result:
GIMP crashes; this is caught by Windows, which produces a generic and unfortunately unhelpful error message stating that the program has encountered a problem and needs to be closed.
Comment 1 gnome-bugzilla 2012-10-17 13:00:07 UTC
I've not been able to find debug symbols for GIMP's windows build, but perhaps the following (from the crash dump) might be useful anyway:

--- CUT HERE ---

Loading Dump File [C:\Users\XXX\AppData\Local\CrashDumps\gimp-2.8.exe.13992.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
Windows Server 2008/Windows Vista Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Wed Oct 17 14:31:33.000 2012 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:00:14.000
................................................................
........................
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(36a8.4a98): Access violation - code c0000005 (first/second chance not available)
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntdll.dll - 
*** ERROR: Module load completed but symbols could not be loaded for gimp-2.8.exe
eax=00001d07 ebx=065fe698 ecx=00002000 edx=00001d07 esi=027930b0 edi=06199408
eip=006f1ad2 esp=0022fb20 ebp=00000000 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210202
gimp_2_8+0x2f1ad2:
006f1ad2 394500          cmp     dword ptr [ebp],eax  ss:0023:00000000=????????

--- CUT HERE ---
Comment 2 Max Mustermann 2012-10-20 10:41:51 UTC
Thank you for the bug report and your efforts in providing stacktraces.
I tried to reproduce with GIMP 2.8.2 on Win7, 32 bit, but everything goes fine here. When opening the file GIMP tells me that the image includes the Adobe RGB color profile and asks me to keep or convert it to sRGB. Do you get this question, too, and if yes, what did you choose?
Is your Vista 32 or 64 bit?
What happens, if you remove the embedded color profile with another application and then reopen it in GIMP?
The stacktrace doesn't tell much, because it misses debug symbols. Can you start GIMP with the parameters --stack-trace-mode=always --version --verbose and post the output here?
Your answer within the next 6 weeks is appreciated. Thank you in advance.
Comment 3 gnome-bugzilla 2012-10-20 11:11:52 UTC
Hi Sven,

thanks for your reply. To answer your questions:

1) There is no such dialogue when I try to open this file; GIMP crashes immediately.
2) 32 bit.
3) I've run the image through jhead -purejpg; the resulting file opens just fine in GIMP.
4) Output of gimp-2.8 --stack-trace-mode=always --version --verbose:

GNU Image Manipulation Program version 2.8.2
git-describe: GIMP_2_8_0-194-ga42a02e

using GEGL version 0.2.0 (compiled against version 0.2.0)
using GLib version 2.32.3 (compiled against version 2.32.3)
using GdkPixbuf version 2.26.1 (compiled against version 2.26.1)
using GTK+ version 2.24.10 (compiled against version 2.24.10)
using Pango version 1.30.0 (compiled against version 1.30.0)
using Fontconfig version 2.9.0 (compiled against version 2.9.0)
using Cairo version 1.10.2 (compiled against version 1.10.2)
(Type any character to close this window)
Comment 4 Goodwin 2012-10-21 15:27:49 UTC
Hello,

I think, I have the same Issue on Windows XP 32 bits SP3. With old version of Gimp 2.6 or 2.5 from which I have upgraded 14 days agao, the same picture has been opened without any problems.

I get additionally tin GIMP following messages ( I use the czech version):

Zásuvný modul se zhroutil: „file-jpeg.exe“
(C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins\file-jpeg.exe)

(what means, the plugin module "file-jpeg.exe" has crashed)

And the second one:

Otevírání „C:\Temp\black.jpg“ selhalo: Procedura „file-jpeg-load“ nevrátila návratovou hodnotu

(What means, the given file failed to open - The procedure file-jpeg-load has returned no result value)
Comment 5 Max Mustermann 2012-10-31 20:20:39 UTC
Thank you, gnome-bugzilla, for reporting back. I checked the metadata of the file you referred but found nothing conspicuous. As you reported it works now I think we should see the problem as resolved. 
Goodwin, your problem is appearantly a duplicate of bug #682454. 

Crashing GIMP on importing JPEG files is a problem we hear from time to time and have already made some efforts to solve this. If you have further problems with this, please try the latest GIMP stable build (2.8. series) from http://nightly.darkrefraction.com/gimp/.

Please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 682454 ***