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
Created attachment 801197 [details] File: backtrace
Created attachment 801198 [details] File: cgroup
Created attachment 801199 [details] File: core_backtrace
Created attachment 801200 [details] File: dso_list
Created attachment 801201 [details] File: environ
Created attachment 801202 [details] File: exploitable
Created attachment 801203 [details] File: limits
Created attachment 801204 [details] File: maps
Created attachment 801205 [details] File: open_fds
Created attachment 801206 [details] File: proc_pid_status
Created attachment 801207 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?