Bug 1475362

Summary: [abrt] gimp: combine_mask_and_alpha_channel_stroke(): gimp-2.8 killed by signal 11
Product: [Fedora] Fedora Reporter: ell1e <el>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: el, jridky, nphilipp, phracek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/affa9d60b95b5d9b197e5696350f09ae715dfa9b
Whiteboard: abrt_hash:e5091c43028f68ae7656a042c8e4aaea5ebc22ab;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-04 23:51:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ell1e 2017-07-26 13:50:03 UTC 
Version-Release number of selected component:
gimp-2.8.22-2.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        gimp-2.8
crash_function: combine_mask_and_alpha_channel_stroke
executable:     /usr/bin/gimp-2.8
journald_cursor: s=26ba0c023611487a89de19e7b4de4b70;i=b751;b=e41cca87b0b0413b8d8d57f6ddeb8a1d;m=8f189d7c;t=55538ab256504;x=ca7631d62c9a3364
kernel:         4.11.8-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 combine_mask_and_alpha_channel_stroke at paint-funcs-generic.h:648
 #1 combine_mask_and_sub_region_stroke at paint-funcs.c:3785
 #2 do_parallel_regions_single at pixel-processor.c:214
 #3 pixel_regions_do_parallel at pixel-processor.c:337
 #4 pixel_regions_process_parallel_valist at pixel-processor.c:406
 #5 pixel_regions_process_parallel at pixel-processor.c:479
 #6 combine_mask_and_region at paint-funcs.c:3803
 #7 paint_mask_to_canvas_tiles at gimppaintcore.c:1215
 #8 gimp_paint_core_paste at gimppaintcore.c:971
 #9 gimp_brush_core_paste_canvas at gimpbrushcore.c:945
Comment 1 ell1e 2017-07-26 13:50:11 UTC 
Created attachment 1304807 [details]
File: backtrace
Comment 2 ell1e 2017-07-26 13:50:13 UTC 
Created attachment 1304808 [details]
File: cgroup
Comment 3 ell1e 2017-07-26 13:50:15 UTC 
Created attachment 1304809 [details]
File: core_backtrace
Comment 4 ell1e 2017-07-26 13:50:17 UTC 
Created attachment 1304810 [details]
File: cpuinfo
Comment 5 ell1e 2017-07-26 13:50:19 UTC 
Created attachment 1304811 [details]
File: dso_list
Comment 6 ell1e 2017-07-26 13:50:20 UTC 
Created attachment 1304812 [details]
File: environ
Comment 7 ell1e 2017-07-26 13:50:22 UTC 
Created attachment 1304813 [details]
File: exploitable
Comment 8 ell1e 2017-07-26 13:50:24 UTC 
Created attachment 1304814 [details]
File: limits
Comment 9 ell1e 2017-07-26 13:50:27 UTC 
Created attachment 1304815 [details]
File: maps
Comment 10 ell1e 2017-07-26 13:50:28 UTC 
Created attachment 1304816 [details]
File: open_fds
Comment 11 ell1e 2017-07-26 13:50:30 UTC 
Created attachment 1304817 [details]
File: proc_pid_status
Comment 12 ell1e 2017-07-26 13:50:31 UTC 
Created attachment 1304818 [details]
File: var_log_messages
Comment 13 Nils Philippsen 2017-07-30 11:54:09 UTC 
Please add details on what you were doing when the crash happened.
Comment 14 ell1e 2017-07-30 12:35:17 UTC 
I really can't remember. All I remember is that I clicked when it happened, but I was doing something in a rush so I don't really recall what I was doing last.
Comment 15 Nils Philippsen 2017-08-04 23:51:37 UTC 
I've opened a bug on the upstream bug tracker here:

https://bugzilla.gnome.org/show_bug.cgi?id=785846

Please consider adding yourself to Cc there. I'll close this bug as UPSTREAM because I don't want to keep track of it in two places ;). Feel free to reopen once a fix is ready, so that we can incorporate it without having to wait for the next public release.