Version-Release number of selected component: gnome-contacts-3.6.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gnome-contacts-search-provider crash_function: magazine_chain_pop_head executable: /usr/libexec/gnome-contacts-search-provider kernel: 3.6.7-5.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Nov 28 22:21:55 localhost abrt[9591]: Saved core dump of pid 9572 (/usr/libexec/gnome-contacts-search-provider) to /var/spool/abrt/ccpp-2012-11-28-22:21:54-9572 (57901056 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:528 #1 thread_memory_magazine1_alloc at gslice.c:835 #2 g_slice_alloc at gslice.c:994 #3 g_slice_alloc0 at gslice.c:1029 #4 g_key_file_init at gkeyfile.c:562 #5 g_key_file_new at gkeyfile.c:626 #6 e_source_init at e-source.c:1579 #7 g_type_create_instance at gtype.c:1890 #8 g_object_constructor at gobject.c:1854 #10 g_object_new_valist at gobject.c:1835
Created attachment 653805 [details] File: backtrace
Created attachment 653806 [details] File: cgroup
Created attachment 653807 [details] File: core_backtrace
Created attachment 653808 [details] File: dso_list
Created attachment 653809 [details] File: environ
Created attachment 653810 [details] File: limits
Created attachment 653811 [details] File: maps
Created attachment 653812 [details] File: open_fds
Created attachment 653813 [details] File: proc_pid_status
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors. I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.