Description of problem: When I open my PNG image using $ gimp pirkko1.png pirkko1.png: PNG image data 10196 x 14024, 8-bit/color RGB, non-interlaced, 148M Version-Release number of selected component: gimp-2.8.8-3.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gimp pirkko2.png crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.0-1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc at gmem.c:109 #3 tile_alloc at tile.c:163 #4 tile_lock at tile.c:95 #5 tile_manager_get at tile-manager.c:309 #6 pixel_region_configure at pixel-region.c:565 #7 pixel_regions_configure at pixel-region.c:547 #8 pixel_regions_process at pixel-region.c:381 #9 gimp_channel_real_is_empty at gimpchannel.c:1213 #10 select_actions_update at select-actions.c:156 #11 gimp_ui_manager_real_update at gimpuimanager.c:391
Created attachment 824128 [details] File: backtrace
Created attachment 824129 [details] File: cgroup
Created attachment 824130 [details] File: core_backtrace
Created attachment 824131 [details] File: dso_list
Created attachment 824132 [details] File: environ
Created attachment 824133 [details] File: limits
Created attachment 824134 [details] File: maps
Created attachment 824135 [details] File: open_fds
Created attachment 824136 [details] File: proc_pid_status
Created attachment 824137 [details] File: var_log_messages
Created attachment 824138 [details] File: binary
I think it's best if we handled this upstream: http://bugzilla.gnome.org/show_bug.cgi?id=712330
For me at least, increasing the kernel's vm.max_map_count parameter fixes this issue. See https://bugzilla.gnome.org/show_bug.cgi?id=712330#c8
Another user experienced a similar problem: sometimes .nef->.jpeg export crashes. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /bin/gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.6-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Gimp crash during editing (rotation) of a photo. Approximately 3 other photos were open at the same time. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gimp-2.8 /home/enright/Pictures/2014-01-04/IMG_4190.JPG crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.6-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 500
Another user experienced a similar problem: This happened while using Gausian blur, however after Fedora upgrade (from 17 to 20) and hardware hange (from Lenovo T500 to Toshiba Satellite P70-A) GIMP crashes frequently and almost randomly. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.6-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1001
Confirmed, it is a 3.12 kernel issue, and increasing vm.max_map_count fixes the crash. Thank YOU!!! This issue has been killing me. Mr Grisby, you just saved my life. For those who don't know how: $ sudo sysctl -e vm.max_map_count=131060 To know how many maps are used: $ wc -l /proc/$(pidof gimp)/maps. 68064 with the image I was trying to open tonight. Another workaround proposed by a GIMP developer: run: $ MALLOC_MMAP_MAX_=0 gimp
Another user experienced a similar problem: ran the 'lomo' plugin in gimp. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gimp /tmp/DSC_0704.NEF_8CEX9W.ufraw crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.7-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
*** Bug 1048498 has been marked as a duplicate of this bug. ***
*** Bug 1049140 has been marked as a duplicate of this bug. ***
as root, sysctl vm.max_map_count=16777216 fixed this for me. thanks people.
Another user experienced a similar problem: I tried to add some text-layer. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gimp-2.8 /home/besser82/Downloads/FOC-Antrag%20Bj%C3%B6rn%20Esser.pdf crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.8-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Loading 130MB tiff file reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.8-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1209
Another user experienced a similar problem: Pasting clibboard (rather large, cca 6500x4800px) to a new image. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gimp-2.8 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.9-301.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Working with pictures reporter: libreport-2.1.12 backtrace_rating: 4 crash_function: g_malloc executable: /usr/bin/gimp-2.8 kernel: 3.12.10-300.fc20.x86_64 package: gimp-2.8.10-4.fc20 reason: gimp-2.8 killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
$ uname -r 3.13.3-201.fc20.x86_64 Seems to be fixed \o/
As the original reporter of the bug I can confirm that recent kernels have been fixed and this bug can be closed.
Closing as per comment #27.