Bug 882956

Summary: [abrt] epiphany-3.6.1-2.fc18: ephy_dialog_get_type@plt: 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:acb1828d6c89f1ddfa2f72e39abc1e3088e91350
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-10 09:17: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: 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-12-03 13:33:08 UTC 
Description of problem:
epiphany doesn't start

Version-Release number of selected component:
epiphany-3.6.1-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        epiphany
crash_function: ephy_dialog_get_type@plt
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 ephy_dialog_get_type@plt at /usr/lib64/epiphany/3.6/extensions/libextensionsmanageruiextension.so
 #1 extensions_manager_ui_register_type at extensions-manager-ui.c:91
 #2 register_module at extension.c:44
 #3 ephy_module_load at ephy-module.c:122
 #4 g_type_module_use at gtypemodule.c:256
 #5 impl_get_object at ephy-shlib-loader.c:188
 #6 load_extension at ephy-extensions-manager.c:532
 #7 sync_loaded_extensions at ephy-extensions-manager.c:680
 #8 ephy_extensions_manager_startup at ephy-extensions-manager.c:957
 #9 ephy_shell_get_extensions_manager at ephy-shell.c:927
Comment 1 Jan Teichmann 2012-12-03 13:33:19 UTC 
Created attachment 656620 [details]
File: backtrace
Comment 2 Jan Teichmann 2012-12-03 13:33:25 UTC 
Created attachment 656621 [details]
File: cgroup
Comment 3 Jan Teichmann 2012-12-03 13:33:31 UTC 
Created attachment 656622 [details]
File: core_backtrace
Comment 4 Jan Teichmann 2012-12-03 13:33:40 UTC 
Created attachment 656623 [details]
File: dso_list
Comment 5 Jan Teichmann 2012-12-03 13:33:47 UTC 
Created attachment 656624 [details]
File: environ
Comment 6 Jan Teichmann 2012-12-03 13:33:57 UTC 
Created attachment 656625 [details]
File: limits
Comment 7 Jan Teichmann 2012-12-03 13:34:03 UTC 
Created attachment 656626 [details]
File: maps
Comment 8 Jan Teichmann 2012-12-03 13:34:08 UTC 
Created attachment 656627 [details]
File: open_fds
Comment 9 Jan Teichmann 2012-12-03 13:34:15 UTC 
Created attachment 656628 [details]
File: proc_pid_status
Comment 10 Jan Teichmann 2012-12-03 13:34:20 UTC 
Created attachment 656629 [details]
File: var_log_messages
Comment 11 Jan Teichmann 2013-01-10 09:17: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.