Bug 845151 - [abrt] gimp-2.8.0-1.fc17: g_logv: Process /usr/bin/gimp-2.8 was killed by signal 5 (SIGTRAP)
[abrt] gimp-2.8.0-1.fc17: g_logv: Process /usr/bin/gimp-2.8 was killed by sig...
Product: Fedora
Classification: Fedora
Component: gimp (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nils Philippsen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-08-01 21:33 EDT by Jeff Peeler
Modified: 2012-11-14 10:49 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-11-14 10:49:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (39.21 KB, text/plain)
2012-08-01 21:33 EDT, Jeff Peeler
no flags Details
File: maps (46.65 KB, text/plain)
2012-08-01 21:33 EDT, Jeff Peeler
no flags Details
File: dso_list (8.87 KB, text/plain)
2012-08-01 21:34 EDT, Jeff Peeler
no flags Details
abrt log (108.57 KB, text/plain)
2012-08-02 12:19 EDT, Jeff Peeler
no flags Details

  None (edit)
Description Jeff Peeler 2012-08-01 21:33:53 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        gimp-2.8 /home/jpeeler/Documents/irmo/check/water.jpg
comment:        Was just resizing the brush / moving the toolbar
crash_function: g_logv
executable:     /usr/bin/gimp-2.8
kernel:         3.4.6-2.fc17.x86_64
pid:            2015
pwd:            /home/jpeeler
remote_result:  691795
time:           Wed 01 Aug 2012 09:20:14 PM EDT
uid:            1000
username:       jpeeler

backtrace:      Text file, 40148 bytes
dso_list:       Text file, 9084 bytes
maps:           Text file, 47770 bytes


:8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x4e801 g_logv libglib-2.0.so.0 -
:8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x4e992 g_log libglib-2.0.so.0 -
:fd952473da735f9c0f50de231aa3d84d7855ef57 0x6a238 - libgdk-x11-2.0.so.0 -
:48c0fe9b8cd26b4d0b5bf1de0bc76da565bd7d27 0x45526 _XError libX11.so.6 -
:48c0fe9b8cd26b4d0b5bf1de0bc76da565bd7d27 0x42771 - libX11.so.6 -
:48c0fe9b8cd26b4d0b5bf1de0bc76da565bd7d27 0x427b5 - libX11.so.6 -
:48c0fe9b8cd26b4d0b5bf1de0bc76da565bd7d27 0x43045 _XEventsQueued libX11.so.6 -
:48c0fe9b8cd26b4d0b5bf1de0bc76da565bd7d27 0x245fa XFlush libX11.so.6 -
:fd952473da735f9c0f50de231aa3d84d7855ef57 0x42410 gdk_window_process_all_updates libgdk-x11-2.0.so.0 -
:23d1440088fed14354e355ac2cbdba1f38fcf1a3 0xc0fb1 - libgtk-x11-2.0.so.0 -
:fd952473da735f9c0f50de231aa3d84d7855ef57 0x1eb97 - libgdk-x11-2.0.so.0 -
:8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x47695 g_main_context_dispatch libglib-2.0.so.0 -
:8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x479c8 - libglib-2.0.so.0 -
:8c083e0f61deb55917e5c7b193fe4d000a7375f1 0x47dc2 g_main_loop_run libglib-2.0.so.0 -
:fd3b4b06b698fed8a4803cb4e7d1e5b153f36c79 0xb8e98 app_run [pie] -
:fd3b4b06b698fed8a4803cb4e7d1e5b153f36c79 0xb8946 main [pie] -

:'PS1=[\\u@\\h \\W$(__git_ps1 \" (%s)\")]\\$ '
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'

:Limit                     Soft Limit           Hard Limit           Units     
:Max cpu time              unlimited            unlimited            seconds   
:Max file size             unlimited            unlimited            bytes     
:Max data size             unlimited            unlimited            bytes     
:Max stack size            8388608              unlimited            bytes     
:Max core file size        0                    unlimited            bytes     
:Max resident set          unlimited            unlimited            bytes     
:Max processes             1024                 30533                processes 
:Max open files            1024                 4096                 files     
:Max locked memory         65536                65536                bytes     
:Max address space         unlimited            unlimited            bytes     
:Max file locks            unlimited            unlimited            locks     
:Max pending signals       30533                30533                signals   
:Max msgqueue size         819200               819200               bytes     
:Max nice priority         0                    0                    
:Max realtime priority     0                    0                    
:Max realtime timeout      unlimited            unlimited            us        

:pos:	0
:flags:	0100000
:pos:	5226
:flags:	0102002
:pos:	5226
:flags:	0102002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004000
:pos:	0
:flags:	00
:pos:	57000704
:flags:	0100002

:Jul 31 11:18:20 jbp-laptop yum[16409]: Installed: 2:gimp-2.8.0-1.fc17.x86_64
:Aug  1 21:12:02 jbp-laptop kernel: [215496.362764] gimp-2.8[8784]: segfault at 2 ip 00007f556fe829e6 sp 00007fffffcca7a0 error 4 in gimp-2.8[7f556fb17000+580000]
:Aug  1 21:12:03 jbp-laptop abrt[11122]: Saved core dump of pid 8784 (/usr/bin/gimp-2.8) to /var/spool/abrt/ccpp-2012-08-01-21:12:02-8784 (168304640 bytes)
:Aug  1 21:20:14 jbp-laptop kernel: [  456.620775] gimp-2.8[2015] trap int3 ip:7fa80e8b9801 sp:7fff628a5000 error:0
:Aug  1 21:20:15 jbp-laptop abrt[3057]: Saved core dump of pid 2015 (/usr/bin/gimp-2.8) to /var/spool/abrt/ccpp-2012-08-01-21:20:14-2015 (164507648 bytes)
Comment 1 Jeff Peeler 2012-08-01 21:33:56 EDT
Created attachment 601851 [details]
File: backtrace
Comment 2 Jeff Peeler 2012-08-01 21:33:58 EDT
Created attachment 601852 [details]
File: maps
Comment 3 Jeff Peeler 2012-08-01 21:34:00 EDT
Created attachment 601853 [details]
File: dso_list
Comment 4 Nils Philippsen 2012-08-02 09:55:40 EDT
(In reply to comment #0)
> comment:        Was just resizing the brush / moving the toolbar

Can you reproduce this behavior and/or describe this in more detail?

Something seems to have triggered a BadAlloc response from the X server:

#2  0x00007fa81245f238 in gdk_x_error (display=<optimized out>, error=<optimized out>) at gdkmain-x11.c:486
        buf = "BadAlloc (insufficient resources for operation)", '\000' <repeats 16 times>
        msg = <optimized out>
#3  0x00007fa80e1bf526 in _XError (dpy=dpy@entry=0x7fa8148e9870, rep=rep@entry=0x7fa815e02fb0) at XlibInt.c:1583
        rtn_val = <optimized out>

This means the X server run out of a resource (probably a pixmap, request code 53). If you can reproduce the problem, please run gimp from the command line with the option "--sync" and re-generate the backtrace -- this will process X protocol requests synchronously and therefore should provide more detail on what the application tried to do. Thanks!
Comment 5 Jeff Peeler 2012-08-02 12:13:46 EDT
I dragged the tool options into the main area that says "you can drop dockable dialogs here". I then closed the floating toolbox. Next I tried to drag the tool options back outside of the main window, expecting that whatever window needed to be created for it to attach to would spawn itself.

backtrace_rating: 4
Package: gimp-2.8.0-1.fc17
OS Release: Fedora release 17 (Beefy Miracle)
Comment 6 Jeff Peeler 2012-08-02 12:19:59 EDT
Created attachment 601993 [details]
abrt log

The backtraces look the same with the --sync option, but here's everything again.
Comment 8 Nils Philippsen 2012-11-13 11:12:00 EST
Jeff, sorry it took me so long.

Anyway, it looks like GIMP tries to create a pixmap of 1140x59699 pixels which looks a bit large to me. What are the dimensions of your screen? When this happens, I take it that GIMP in multi window mode -- are any of the windows maximized, or have a very large height?
Comment 9 Jeff Peeler 2012-11-13 15:25:49 EST
It's ok, stuff happens.

It appears that this problem has been fixed. But for the record, none of the windows were maximized. This was actually in single-window mode, with a resolution of 1920x1080. I don't use gimp that often, so it could have been fixed a while ago. I think it's safe to close now though.
Comment 10 Nils Philippsen 2012-11-14 10:49:23 EST
Thanks for the quick reply!

I can't imagine why GIMP would want to create such a large pixmap, but good that it's fixed (or at least seem to be). I'll close this for now, if it happens again please reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.