Bug 887315

Summary: [abrt] gimp-2.8.2-6.fc17: g_logv: Process /usr/bin/gimp-2.8 was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Eric <eric.jarpe>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c224b62417fbf53a5ff215d5e129f2829b6a8b2c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 05:55:18 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: xsession_errors
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages
none
File: build_ids none

Description Eric 2012-12-14 16:34:46 UTC
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

Comment 1 Eric 2012-12-14 16:34:49 UTC
Created attachment 663643 [details]
File: core_backtrace

Comment 2 Eric 2012-12-14 16:34:51 UTC
Created attachment 663644 [details]
File: environ

Comment 3 Eric 2012-12-14 16:35:01 UTC
Created attachment 663645 [details]
File: limits

Comment 4 Eric 2012-12-14 16:35:07 UTC
Created attachment 663646 [details]
File: backtrace

Comment 5 Eric 2012-12-14 16:35:09 UTC
Created attachment 663647 [details]
File: cgroup

Comment 6 Eric 2012-12-14 16:35:11 UTC
Created attachment 663648 [details]
File: smolt_data

Comment 7 Eric 2012-12-14 16:35:14 UTC
Created attachment 663649 [details]
File: xsession_errors

Comment 8 Eric 2012-12-14 16:35:16 UTC
Created attachment 663650 [details]
File: executable

Comment 9 Eric 2012-12-14 16:35:18 UTC
Created attachment 663651 [details]
File: maps

Comment 10 Eric 2012-12-14 16:35:26 UTC
Created attachment 663652 [details]
File: dso_list

Comment 11 Eric 2012-12-14 16:35:28 UTC
Created attachment 663653 [details]
File: proc_pid_status

Comment 12 Eric 2012-12-14 16:35:30 UTC
Created attachment 663654 [details]
File: open_fds

Comment 13 Eric 2012-12-14 16:35:38 UTC
Created attachment 663655 [details]
File: var_log_messages

Comment 14 Eric 2012-12-14 16:35:40 UTC
Created attachment 663656 [details]
File: build_ids

Comment 15 Nils Philippsen 2012-12-18 15:29:49 UTC
(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?

Comment 16 Fedora End Of Life 2013-07-04 01:28:30 UTC
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.

Comment 17 Fedora End Of Life 2013-08-01 05:55:22 UTC
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.