Version-Release number of selected component: tracker-0.14.4-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/tracker-store crash_function: strlen executable: /usr/libexec/tracker-store kernel: 3.6.7-5.fc18.x86_64 remote_result: 754708 uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:31 #1 g_strdup at gstrfuncs.c:363 #2 g_error_copy at gerror.c:503 #3 _g_error_copy0 at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:170 #4 tracker_store_sparql_update_co at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:369 #5 tracker_store_task_finish_cb at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:193 #6 __lambda1_ at /home/martyn/Source/tracker/src/tracker-store/tracker-store.vala:246 #7 ___lambda1__gsource_func at tracker-store.c:1356 #12 tracker_main_main at /home/martyn/Source/tracker/src/tracker-store/tracker-main.vala:306 Potential duplicate: bug 754708
Created attachment 656218 [details] File: backtrace
Created attachment 656219 [details] File: cgroup
Created attachment 656220 [details] File: core_backtrace
Created attachment 656221 [details] File: dso_list
Created attachment 656222 [details] File: environ
Created attachment 656223 [details] File: limits
Created attachment 656224 [details] File: maps
Created attachment 656225 [details] File: open_fds
Created attachment 656226 [details] File: proc_pid_status
Created attachment 656227 [details] File: var_log_messages
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.