Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 3 cmdline: /usr/bin/python /usr/share/PackageKit/helpers/yum/yumBackend.py get-updates none executable: /usr/bin/python2.7 kernel: 3.6.7-5.fc18.x86_64 remote_result: 824614 uid: 0 var_log_messages: Nov 27 14:05:02 localhost abrt[7230]: Saved core dump of pid 6610 (/usr/bin/python2.7) to /var/spool/abrt/ccpp-2012-11-27-14:04:57-6610 (187961344 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 visit_decref at /usr/src/debug/Python-2.7.3/Modules/gcmodule.c:320 #2 list_traverse at /usr/src/debug/Python-2.7.3/Objects/listobject.c:2371 #3 subtract_refs at /usr/src/debug/Python-2.7.3/Modules/gcmodule.c:345 #4 collect at /usr/src/debug/Python-2.7.3/Modules/gcmodule.c:874 #5 PyGC_Collect at /usr/src/debug/Python-2.7.3/Modules/gcmodule.c:1386 #6 Py_Finalize at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:444 #8 Py_Exit at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1768 #9 handle_system_exit at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1142 #11 PyErr_PrintEx at /usr/src/debug/Python-2.7.3/Python/pythonrun.c:1152
Created attachment 652913 [details] File: backtrace
Created attachment 652914 [details] File: build_ids
Created attachment 652915 [details] File: cgroup
Created attachment 652916 [details] File: core_backtrace
Created attachment 652917 [details] File: dso_list
Created attachment 652918 [details] File: environ
Created attachment 652919 [details] File: limits
Created attachment 652920 [details] File: maps
Created attachment 652921 [details] File: open_fds
Created attachment 652922 [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.