Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/python /usr/share/PackageKit/helpers/yum/yumBackend.py install-packages only-trusted;simulate gstreamer1-plugins-ugly;1.0.2-2.fc18;x86_64;rpmfusion-free&gstreamer-plugins-bad-free-extras;0.10.23-13.fc18;x86_64;updates-testing&gstreamer-plugins-good-extras;0.10.31-5.fc18;x86_64;fedora crash_function: try_rich_compare executable: /usr/bin/python2.7 kernel: 3.6.9-4.fc18.x86_64 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 try_rich_compare at /usr/src/debug/Python-2.7.3/Objects/object.c:616 #1 do_richcmp at /usr/src/debug/Python-2.7.3/Objects/object.c:925 #2 PyObject_RichCompare at /usr/src/debug/Python-2.7.3/Objects/object.c:977 #3 cmp_outcome at /usr/src/debug/Python-2.7.3/Python/ceval.c:4603 #4 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2361 #5 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4184 #6 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119 #7 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.3/Python/ceval.c:2740 #8 fast_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4184 #9 call_function at /usr/src/debug/Python-2.7.3/Python/ceval.c:4119
Created attachment 661388 [details] File: backtrace
Created attachment 661389 [details] File: cgroup
Created attachment 661390 [details] File: core_backtrace
Created attachment 661391 [details] File: dso_list
Created attachment 661392 [details] File: environ
Created attachment 661393 [details] File: limits
Created attachment 661394 [details] File: maps
Created attachment 661395 [details] File: open_fds
Created attachment 661396 [details] File: proc_pid_status
Created attachment 661397 [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.