did you try the upload with media included? If it worked then this is another windows ok mac not bug.
Of course I did! 4,000+ pieces of media. This particular file is a little larger than my initial test import. This file has 42,218 people, 16,257 families, 80685 events, 5798 places, 2697 citations, 4170 media items, 4575 media links. TreeShared to Ancestry in 62 minutes, synced from FTM2019 to Ancestry in 65 minutes. Everything was accepted as default. Trees were both set to private.
If it is a Mac only bug, then in theory, you should find a Windows computer and try the same process. If it uploads ok, then maybe you have a bug. If it crashes, then you have a problem with your file. However, if it were a Mac specific bug, I am pretty certain that every Mac user would be carping about it in the various RM forums. I would also be interested in what happens if you found someone with a newer Mac and tried this upload. If it works on the newer Mac, then you have an issue with either the file or your hardware, not the software.
no mac user has any interest is using a windows pc and others have reported this issue. Any file problem is created by RM8 import and the failure is a timeout error.
Mac users are not commenting much on RM8 because most have left years ago and the few remaining have developed very low expectations. I am at the stage where RM8 is a modestly useful helper tool for FTM and there is little value in these forums so I will probably drop them.
Alas, but thanks for your help. I have valued the perspective.
I think it is more because you are afraid that it will turn out to be your problem, not the software.
As for Mac users, you would be very wrong. There are now and have been quite a good size number of them commenting throughout the beta testing and community preview sections. I would say the proportion is rather equivalent to the proportion of Mac users to Windows users.
Surely you have a friend, at least one, with a newer Mac that would let you do a quick install and test. I am sure that if you have friends, at least half of them do use Windows machines.
I’m feeling reassured, thanks. And 'tis the season. 
I’m still hoping for better in the New Year. “Hope springs eternal …” Alexander Pope.
Yes, I’m getting frequent access violations on Windows 10. As someone else pointed out, sources seem to be an issue. Another cause is navigating through profiles too fast, especially in pedigree view. Haven’t tried creating a new file or exporting recently.
Thanks for sharing. There is comfort in knowing I’m not alone.
1 Like
Now, children, play nice.
1 Like
That’s an interesting thought. I’ve not thought about monitoring CPU and memory since my old Windows days! Ah, that takes me back! I’ll check it out, thnx.
It isn’t just Rootsmagic that does this. It may surprise you that there are many, many programs that offer that same advice. Even FTM has it on their troubleshooting page for Mac issues.
I have consistently received access errors on my M1 Mac Pro lap book after a number of efforts to unsuccessfully engage the programmers for a fix. The attempt to update the database at a family holiday reunion was a bust. I shall be reverting back to Windows this week. At this time, I do not recommend using the Mac
Don’t you mean 10k people and 41,525 citations. How could you have more people than citations?
Rob,
There are a lot of “name collectors” out there who don’t document sources. They just graft branches from online trees onto their own with little regard for accuracy.
Rich
Fingers crossed that someone on the development team is interested!
Egad! Now I’m confronting the need to upgrade from Mojave in order to try the Monit widget! (The residuals of my obsessive-compulsive condition cannot resist the intrigue of doing something potentially more useful than just cleaning up my database! 
) On the other hand, could my outdated OS (Mojave) be at the root of my Access Violation problems?!!! Help?!
As much as I hate to say this, MEA CULPA! All my complaints about Access Violation errors were my fault! After updating my system from Mohave to Monterey, 12.1, no more access error messages! So much for trying to get by with older OSs!
That is good news. I am stuck on Catalina since Big Sur would brick my 2014 MBP and Monterey will not run on it. Have not other people on M1 macs been getting AVs?
Alas, I can offer nothing more than sympathy. 