Description of problem: A very large image was open. Probably made gimp instable. Version-Release number of selected component: gimp-2.8.2-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gimp-2.8 crash_function: g_logv kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_logv at gmessages.h:101 : #2 g_realloc at gmem.c:229 : #3 tiff_save_write at io-tiff.c:593 : #4 TIFFAppendToStrip at tif_write.c:666 : #5 TIFFFlushData1 at tif_write.c:689 : #6 DumpModeEncode at tif_dumpmode.c:61 : #7 TIFFWriteScanline at tif_write.c:167 : #8 gdk_pixbuf__tiff_image_save_to_callback at io-tiff.c:758 : #9 gdk_pixbuf_real_save_to_callback at gdk-pixbuf-io.c:2189 : #10 gdk_pixbuf_save_to_callbackv at gdk-pixbuf-io.c:2556
Created attachment 663643 [details] File: core_backtrace
Created attachment 663644 [details] File: environ
Created attachment 663645 [details] File: limits
Created attachment 663646 [details] File: backtrace
Created attachment 663647 [details] File: cgroup
Created attachment 663648 [details] File: smolt_data
Created attachment 663649 [details] File: xsession_errors
Created attachment 663650 [details] File: executable
Created attachment 663651 [details] File: maps
Created attachment 663652 [details] File: dso_list
Created attachment 663653 [details] File: proc_pid_status
Created attachment 663654 [details] File: open_fds
Created attachment 663655 [details] File: var_log_messages
Created attachment 663656 [details] File: build_ids
(In reply to comment #0) > Description of problem: > A very large image was open. Probably made gimp instable. Looking at /proc/<pid>/status of the process (attachment 663653 [details]), it shows that it uses up nearly 90% of the available memory (RAM+swap) -- how big was the image you were working on?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.