Bug 1010678

Summary: [abrt] mate-file-manager-1.6.2-3.fc18: slab_allocator_alloc_chunk: Process /usr/bin/caja was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: gmf <giuseppemfusco>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f7e0aab5798d4c5703d6810d6a1bf6503c83e89e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-19 19:50:47 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: 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 gmf 2013-09-22 13:44:27 UTC 
Version-Release number of selected component:
mate-file-manager-1.6.2-3.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        caja -n
crash_function: slab_allocator_alloc_chunk
executable:     /usr/bin/caja
kernel:         3.10.11-100.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 slab_allocator_alloc_chunk at gslice.c:1303
 #1 magazine_cache_pop_magazine at gslice.c:724
 #2 thread_memory_magazine1_reload at gslice.c:794
 #3 g_slice_alloc at gslice.c:992
 #4 g_string_sized_new at gstring.c:126
 #5 g_string_new at gstring.c:158
 #6 eel_strdup_vprintf_with_custom at eel-string.c:722
 #7 f at caja-file-operations.c:914
 #8 report_copy_progress at caja-file-operations.c:2985
 #9 splice_stream_with_progress at gfile.c:2894
Comment 1 gmf 2013-09-22 13:44:33 UTC 
Created attachment 801197 [details]
File: backtrace
Comment 2 gmf 2013-09-22 13:44:36 UTC 
Created attachment 801198 [details]
File: cgroup
Comment 3 gmf 2013-09-22 13:44:40 UTC 
Created attachment 801199 [details]
File: core_backtrace
Comment 4 gmf 2013-09-22 13:44:45 UTC 
Created attachment 801200 [details]
File: dso_list
Comment 5 gmf 2013-09-22 13:44:50 UTC 
Created attachment 801201 [details]
File: environ
Comment 6 gmf 2013-09-22 13:44:54 UTC 
Created attachment 801202 [details]
File: exploitable
Comment 7 gmf 2013-09-22 13:44:57 UTC 
Created attachment 801203 [details]
File: limits
Comment 8 gmf 2013-09-22 13:45:02 UTC 
Created attachment 801204 [details]
File: maps
Comment 9 gmf 2013-09-22 13:45:06 UTC 
Created attachment 801205 [details]
File: open_fds
Comment 10 gmf 2013-09-22 13:45:09 UTC 
Created attachment 801206 [details]
File: proc_pid_status
Comment 11 gmf 2013-09-22 13:45:13 UTC 
Created attachment 801207 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-09-28 15:10:00 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?