Version-Release number of selected component: epiphany-3.6.1-2.fc18 Additional info: backtrace_rating: 4 cmdline: epiphany crash_function: JSC::CodeBlock::updateAllPredictionsAndCountLiveness executable: /usr/bin/epiphany kernel: 3.6.7-5.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 JSC::CodeBlock::updateAllPredictionsAndCountLiveness at /lib64/libjavascriptcoregtk-3.0.so.0 #1 JSC::CodeBlock::updateAllPredictions at /lib64/libjavascriptcoregtk-3.0.so.0 #2 JSC::CodeBlock::visitAggregate at /lib64/libjavascriptcoregtk-3.0.so.0 #3 JSC::FunctionExecutable::visitChildren at /lib64/libjavascriptcoregtk-3.0.so.0 #4 JSC::SlotVisitor::drain at /lib64/libjavascriptcoregtk-3.0.so.0 #5 JSC::Heap::markRoots at /lib64/libjavascriptcoregtk-3.0.so.0 #6 JSC::Heap::collect at /lib64/libjavascriptcoregtk-3.0.so.0 #7 collect at /lib64/libwebkitgtk-3.0.so.0 #8 WebCore::ThreadTimers::sharedTimerFiredInternal at /lib64/libwebkitgtk-3.0.so.0 #9 timeout_cb at /lib64/libwebkitgtk-3.0.so.0
Created attachment 654422 [details] File: backtrace
Created attachment 654423 [details] File: build_ids
Created attachment 654424 [details] File: cgroup
Created attachment 654425 [details] File: core_backtrace
Created attachment 654426 [details] File: dso_list
Created attachment 654427 [details] File: environ
Created attachment 654428 [details] File: limits
Created attachment 654429 [details] File: maps
Created attachment 654430 [details] File: open_fds
Created attachment 654431 [details] File: proc_pid_status
Created attachment 654432 [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.