Bug 882956 - [abrt] epiphany-3.6.1-2.fc18: ephy_dialog_get_type@plt: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] epiphany-3.6.1-2.fc18: ephy_dialog_get_type@plt: Process /usr/bin/epip...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:acb1828d6c89f1ddfa2f72e39ab...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-03 13:33 UTC by Jan Teichmann
Modified: 2013-01-10 09:17 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-10 09:17:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.64 KB, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: core_backtrace (244 bytes, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: dso_list (13.29 KB, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: environ (1.52 KB, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-03 13:33 UTC, Jan Teichmann
no flags Details
File: maps (60.48 KB, text/plain)
2012-12-03 13:34 UTC, Jan Teichmann
no flags Details
File: open_fds (643 bytes, text/plain)
2012-12-03 13:34 UTC, Jan Teichmann
no flags Details
File: proc_pid_status (918 bytes, text/plain)
2012-12-03 13:34 UTC, Jan Teichmann
no flags Details
File: var_log_messages (1.58 KB, text/plain)
2012-12-03 13:34 UTC, Jan Teichmann
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.