Research Help page unresponsive using Chrome
Within the past week or two I have been getting an error message when I try to access any suggestions from the “Research Help” section on the right of my FamilySearch screen. The same thing happens if I attempt to click on “Possible Duplicate.”
After about 60 seconds or so, I get the following message.
Page Unresponsive. You can wait for it to become responsive or exit this page. When I click on “Wait,” I get the same message. When I click on “Exit,” I get the following message.
Aw, Snap! Something went wrong when displaying this webpage. Error Code RESULT_CODE_HUNG
Here’s are things I’ve tried:
Reloading the page does not help.
My internet connection is fine.
Cleared browsing data. Deleted cache and cookies, several times.
Closed other tabs, extensions and apps.
I have shut down FamilySearch and started over, several times.
Restarted my computer, several times.
I am using Chrome as my browser. I have checked to see if I have the latest version of Chrome, and I do.
Curiously, if I switch to Firefox I am able to open any suggestions in “Research Help” and "Possible Duplicate" without a problem. I suppose I could settle for that, but I prefer using Chrome. It’s where all my bookmarks are. Is anyone else having this problem? Any ideas? Is there a setting on Chrome I can change? I have a feeling that this has something to do with how Chrome is interacting with FamilySearch. I am able to access other sites using Chrome without a hitch – just having a problem with FamilySearch. Thanks.
Answers
-
@L. S. C. Thank you for letting us know. This has been forwarded to the appropriate group.
0 -
Thank you for asking. This has happened a total of three times, once while I was right in the middle of using the feature, "Research Help." It suddenly became unresponsive. In each case I did everything I could think of to resolve the issue, to no avail. After time, the issue seemed to correct itself with no help from me. To date, I am not still experiencing this issue. I am hoping that whatever was causing the issue self corrected.
0
