Description of problem:
Whenever I load a succession of camera-retrieved large .jpg images, crop and scale a portion of them, and export them to .png, eventually GIMP crashes or hangs the system, apparently running out of memory in an 16GB system. I can expect this as early as the third image, or as late as the fifth, but rarely longer. In this instance, GIMP hung at the point where I would have seen the export dialog, and eventually -- after about 10 minutes -- it killed the X session. It was not necessary to reboot, and daemons were not affected.
Note that in the case of each loaded image original, once I select a portion to crop and paste into a new image, I always close the original using 'Discard without Saving'; I mention this in case it may be relevant to the OOM issue. The swapfile is 8GB. The /boot, /, and /home filesystems are all ext4 with full filesystem dm-luks encryption, on a Samsung 840 EVO 250GB SSD.
Version-Release number of selected component:
cmdline: /usr/bin/gimp-2.8 /home/humpher/Pictures/2014-07-04/IMG_1809.JPG
runlevel: N 5
Thread no. 1 (10 frames)
#0 strcmp at ../sysdeps/x86_64/strcmp.S:209
#1 g_str_equal at ghash.c:1706
#2 g_hash_table_lookup_node at ghash.c:386
#3 g_hash_table_lookup at ghash.c:1076
#4 gimp_filename_to_utf8 at gimputils.c:225
#5 gimp_eek at errors.c:182
#6 gimp_terminate at errors.c:142
#7 gimp_sigfatal_handler at signals.c:89
#9 poll at ../sysdeps/unix/syscall-template.S:81
#10 g_main_context_poll at gmain.c:4007
Created attachment 925027 [details]
Created attachment 925028 [details]
Created attachment 925029 [details]
Created attachment 925030 [details]
Created attachment 925031 [details]
Created attachment 925032 [details]
Created attachment 925033 [details]
Created attachment 925034 [details]
Created attachment 925035 [details]
Created attachment 925036 [details]
Created attachment 925037 [details]
You mention large JPEG Images, how large are they?
Have you customized memory environment settings (Edit/Preferences -> Environment)? Please attach your ~/.gimp-2.8/gimprc. Thanks!
The 'large' original (source) JPEG images are all 1.0 MiB to 4.0 MiB.
The Environment dialog settings are all defaults except for undo which is 10.
Minimal number of undo levels: 10
Maximum undo memory: 64 Megabytes
Tile cache size: 8193366 Kilobytes
Maximum new image size: 128 Megabytes
Number of processors to use: 8
Size of thumbnails: Normal (128x128)
Maximum filesize for thumbnailing: 4 Megabytes
_X_ Confirm closing of unsaved images
_X_ Keep record of used files in the Recent Documents list
# GIMP gimprc
# This is your personal gimprc file. Any variable defined in this file takes
# precedence over the value defined in the system-wide gimprc:
# Most values can be set within GIMP by changing some options in the
# Preferences dialog.
# end of gimprc
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.