Bug 881882

Summary: [abrt] epiphany-3.6.1-2.fc18: JSC::CodeBlock::updateAllPredictionsAndCountLiveness: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: epiphanyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: debarshir, gecko-bugs-nobody, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9ccd588b28a13df98fe02dbd69afb694fd33f300
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 09:19:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jan Teichmann 2012-11-29 18:06:51 UTC 
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
Comment 1 Jan Teichmann 2012-11-29 18:07:35 UTC 
Created attachment 654422 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-11-29 18:07:37 UTC 
Created attachment 654423 [details]
File: build_ids
Comment 3 Jan Teichmann 2012-11-29 18:07:40 UTC 
Created attachment 654424 [details]
File: cgroup
Comment 4 Jan Teichmann 2012-11-29 18:07:42 UTC 
Created attachment 654425 [details]
File: core_backtrace
Comment 5 Jan Teichmann 2012-11-29 18:07:45 UTC 
Created attachment 654426 [details]
File: dso_list
Comment 6 Jan Teichmann 2012-11-29 18:07:47 UTC 
Created attachment 654427 [details]
File: environ
Comment 7 Jan Teichmann 2012-11-29 18:07:49 UTC 
Created attachment 654428 [details]
File: limits
Comment 8 Jan Teichmann 2012-11-29 18:07:52 UTC 
Created attachment 654429 [details]
File: maps
Comment 9 Jan Teichmann 2012-11-29 18:07:54 UTC 
Created attachment 654430 [details]
File: open_fds
Comment 10 Jan Teichmann 2012-11-29 18:07:56 UTC 
Created attachment 654431 [details]
File: proc_pid_status
Comment 11 Jan Teichmann 2012-11-29 18:07:58 UTC 
Created attachment 654432 [details]
File: var_log_messages
Comment 12 Jan Teichmann 2013-01-10 09:19:08 UTC 
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.