Full name indexing keeps crashing and crashes upon reload
Okay, I realize this is the third time I've started a 'crashing' topic, but this one is kind of inconvenient. Now when family search crashes, reloading the page doesn't do any good. Moreover, I run into situations where it crashes right when I'm loading in, and all I can do to get past it is go back and start in to a new record search attempt. (In both cases) Sometimes the new record search attempt will lead to another crash, requiring me to search several times before I can find a viable record.
Answers
-
@AnthonyHopkins5 I will send this up the line to see if we can get someone to look into why it keeps crashing and what can be done in regards to your conversation and the previous conversation.
0 -
@AnthonyHopkins5 can you confirm your browser and operating system levels are compliant with FS requirements please (see https://www.familysearch.org/en/help/helpcenter/article/which-internet-browsers-are-compatible). Thanks.
1 -
It seemed to stop on its own, sorry for not coming back here to answer, but when the issue vanished, I forgot about this string.
0 -
This is still happening for me. Not all the time, but often enough that it's annoying. It also seems to be, every once in a while, repeating the same name checks dozens of times.
0 -
@KathrynAS can you provide some additional information? Are you on the web or the Get Involved app? Which operating system are you using? Can you tell us anything about when it crashes? Is there any kind of pattern?
1 -
Also, if they are on the web, they might try running the browser in incognito or private mode, to see if there's something in the cache, that once removed from the process via using that mode, stops the crashing.
They can try clearing their cache if that appears to be so, but I usually reserve that last step for if other things fail.
One can often right click on the shortcut to the browser and that will bring up a menu that includes the incognito or private mode.
0 -
Sundays are a popular day for Get Involved so it could also be that millions of users could create a temporary 'crash' give your app or computer a few minutes to 'catch its breath' 😊
2
