Description of problem: Loading an 8 mpx image from SD Card. Version-Release number of selected component: gimp-2.8.10-4.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 /run/media/bar/3062-6539/DCIM/100D3100/DSC_0247.JPG /run/media/bar/3062-6539/DCIM/100D3100/DSC_0246.JPG crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.5-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 11504 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc at gmem.c:164 #3 tile_alloc at tile.c:163 #4 tile_lock at tile.c:95 #5 tile_manager_get at tile-manager.c:309 #6 tile_manager_get_at at tile-manager.c:329 #7 tile_pyramid_validate_upper_tile at tile-pyramid.c:430 #8 tile_manager_get at tile-manager.c:309 #9 tile_manager_get_at at tile-manager.c:329 #10 tile_pyramid_validate_upper_tile at tile-pyramid.c:430 #11 tile_manager_get at tile-manager.c:309 Potential duplicate: bug 1030624
Created attachment 842578 [details] File: backtrace
Created attachment 842579 [details] File: cgroup
Created attachment 842580 [details] File: core_backtrace
Created attachment 842581 [details] File: dso_list
Created attachment 842582 [details] File: environ
Created attachment 842583 [details] File: limits
Created attachment 842584 [details] File: maps
Created attachment 842585 [details] File: open_fds
Created attachment 842586 [details] File: proc_pid_status
Created attachment 842587 [details] File: var_log_messages
Another user experienced a similar problem: It usually happens when I do not save the *.xcf file after doing multiple GIMP operations on it. Usually the file is large, as I may be composing an image from 4-6 layers, each itself a photograph of around 3-4 Mb in size with a 16 megapixel resolution from a digital camera. I usually work from a 32 Gb USB key rather than from the laptop (Toshiba Satelite L500) hardrive. [ Simply because I keep the OS and Apps on the local Drive and the Data on a very relaible Key - or set of keys. I seem to avoid the issue if I use small data sets or save the *.xcf to the USB key after every 2-3 big operations, eg; Layer boundery increase, blend tool on filled boundary, create multiple layers for unusual boundary, then I'd save. Also, if I resize an image by fit image to layers - then it is best to save the *.xcf. There is no one particular circumstance at which this error arises from my point of view. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.5-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I tried to import a pdf file having a picture, increasing its resolution to about 900 pixels/in. GIMP hanged for a while and so the system. After a while GIMP crashed. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 /home/ crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.6-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I had two big images open and tried to open a third. Partway through loading the image the progress bar stopped moving, and a short while later all of Gimp's windows disappeared. Some swapping might have been expected, but the system was not out of memory. There was plenty of swap space left. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 /home/beorn/viktigt/meriter/skanna0005.png crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.5-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Attempting to export 250 layers of jpegs as an animated gif. The following error message was given: (gimp:22175): GLib-ERROR **: gmem.c:165: failed to allocate 4096 bytes (file-gif-save:24078): LibGimpBase-WARNING **: file-gif-save: gimp_wire_read(): error reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.7-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I had been creating a blank page when GIMP crashed. It seemed that the page was too big. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.7-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This is the same issue as bug #1030624 on Fedora 20.
Another user experienced a similar problem: random crah after some time working in gimp (rather large file of 8k by 5k pixel, crashes at different time every time) reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 /home/f.ludwig/Insync/Leijuna-gfx/2014-01-23-islands_merged.psd crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.7-200.fc19.x86_64 package: gimp-2.8.10-4.fc19 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.