Bug 1080205 - [abrt] mate-window-manager: g_try_malloc(): marco killed by SIGSEGV
Summary: [abrt] mate-window-manager: g_try_malloc(): marco killed by SIGSEGV
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-window-manager
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f6e77d1b76cc71ea91cdb080c59...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-24 21:58 UTC by Fedor Butikov
Modified: 2014-04-19 23:16 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-19 23:16:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (50.64 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: cgroup (172 bytes, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: core_backtrace (18.23 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: dso_list (11.05 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: environ (1.63 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: limits (1.29 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: maps (53.94 KB, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: open_fds (955 bytes, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: proc_pid_status (943 bytes, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: var_log_messages (344 bytes, text/plain)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details
File: exploitable (168 bytes, application/octet-stream)
2014-03-24 21:58 UTC, Fedor Butikov
no flags Details

Description Fedor Butikov 2014-03-24 21:58:00 UTC
Version-Release number of selected component:
mate-window-manager-1.6.2-6.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        marco
crash_function: g_try_malloc
executable:     /usr/bin/marco
kernel:         3.13.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 g_try_malloc at gmem.c:255
 #4 gdk_pixbuf_copy at gdk-pixbuf.c:482
 #5 dimm_icon at ui/tabpopup.c:125
 #6 tab_entry_new at ui/tabpopup.c:202
 #7 meta_ui_tab_popup_new at ui/tabpopup.c:273
 #8 meta_screen_ensure_tab_popup at core/screen.c:1379
 #9 meta_display_begin_grab_op at core/display.c:3628
 #10 do_choose_window at core/keybindings.c:2902
 #11 handle_switch at core/keybindings.c:2961
 #12 process_event at core/keybindings.c:1218

Comment 1 Fedor Butikov 2014-03-24 21:58:05 UTC
Created attachment 878186 [details]
File: backtrace

Comment 2 Fedor Butikov 2014-03-24 21:58:07 UTC
Created attachment 878187 [details]
File: cgroup

Comment 3 Fedor Butikov 2014-03-24 21:58:10 UTC
Created attachment 878188 [details]
File: core_backtrace

Comment 4 Fedor Butikov 2014-03-24 21:58:12 UTC
Created attachment 878189 [details]
File: dso_list

Comment 5 Fedor Butikov 2014-03-24 21:58:15 UTC
Created attachment 878190 [details]
File: environ

Comment 6 Fedor Butikov 2014-03-24 21:58:17 UTC
Created attachment 878191 [details]
File: limits

Comment 7 Fedor Butikov 2014-03-24 21:58:20 UTC
Created attachment 878192 [details]
File: maps

Comment 8 Fedor Butikov 2014-03-24 21:58:22 UTC
Created attachment 878193 [details]
File: open_fds

Comment 9 Fedor Butikov 2014-03-24 21:58:24 UTC
Created attachment 878194 [details]
File: proc_pid_status

Comment 10 Fedor Butikov 2014-03-24 21:58:26 UTC
Created attachment 878195 [details]
File: var_log_messages

Comment 11 Fedor Butikov 2014-03-24 21:58:28 UTC
Created attachment 878196 [details]
File: exploitable

Comment 12 Wolfgang Ulbrich 2014-04-02 15:22:06 UTC
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?

Comment 13 Wolfgang Ulbrich 2014-04-19 23:16:06 UTC
feel free to post here if it happens again


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