Just installed the 220.127.116.11 update and tried to download a tree from Ancestry. It still fails, but the error window has changed and now has a retry countdown. Cancel just restarts the countdown and the only way out is to force quit.
Hi Larry. I have the same problem on my Mac with a 26000 record tree. It always hangs at around 90%. My Windows versions have no problem downloading the tree. I suspect that the Mac software is actually running in a wrapper which also makes it much slower than Windows. If I copy the backup file from windows across it opens perfectly - and that’s how I use the Mac
You might want to check out this thread if you haven’t already. Seems that there’s a slight difference in the way RM indexes the db based on OS and a best practice is to run the tools to reindex after moving a rm9 file between mac and windows environments.
Thanks Kevin. I’ll look into that.
All my kids are into Apple tech and, if and when, I can get them interested in the tree they will need to have it in their format to continue with.
Personally I don’t like Windows, preferring Linux and then Mac, (I have all 3) but, there are a few things that I have to use Windows for- right now RM is one of them.
No wrapper but still intel only code requiring Rosetta translation. That plus a less than professional mac version causes issues as reflected in very high cpu usage even at idle.
simple comparison of cpu usage in activity monitor and istatistica clearly shows AM does not report overall app activity but is focused on individual processes.
Just installed the 9.1.1 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
Just installed the 9.1.2 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
@LarryD FYI-- when there is a new update, RM always posts the info under News and Announcements with an explanation of what was FIXED…
If it doesn’t say Tree Share in the announcement then nothing on Tree Share was fixed…
Last update said
Fixed: Some Mac users couldn’t log in (or stay connected) to FamilySearch
Fixed: Mac users weren’t able to “Unmatch” on the FamilySearch person tools
Hi Nancy, Thank you. I do read what has been fixed with each update, but since this mentioned a connection issue ( which I believe is the issue with TreeShare ), I was just being optimistic. Also, I want RM to know that the issue still exists and will repost with every update until the issue is fixed.