New RootsMagic Update (10.0.8)
rootsmagician RootsMagician
- Fixed: Clicking arrows in descendant view w/ 2 generations could cause a crash
Kind of confused abt this fix–don’t remember anyone saying it caused a crash–just an access violation
Well, an access violation is pretty crashy. You need to shut down RM and restart it after an access violation. But you are correct that RM doesn’t literally crash and lockup or crash and go away when there is an access violation.
What I’m more interested in is whether any other causes of access violations are fixed, or if it’s only the back arrow on Descendant View. I’m staying with the 32-bit version for now to see what happens with access violations.
3 Likes
interesting – I wonder if there are any stats on if 64b vs 32bit versions have more/less issues.
If so, what system they were on (Mac / pc / W10 /W11 ) etc.
Kevin
1 Like
current macs are 64 bit apple silicon (arm code) and RM is still Intel only code requiring translation by Rosetta which is going away soon.
Understand what you are saying Jerry BUT the FIX did NOT take care of the access violation on even just 2 generations showing-- tried it last night after updating to RM 10.0.8 and it still happened-- and will also note that the original access violation happened when you had 2 or more generations showing
3 Likes
That’s too bad. I’m still on 32-bit and I hadn’t checked the 64 bit exe file. I was just sort of trusting that the fixed worked on the 64-bit version. So I updated the 64-bit version to 10.0.8 just now. You are correct. It still gets the access violation error. My test case is a person with no children or spouse who is in the primary position.
I also tried running the 64-bit 10.0.8 in administrator mode because sometimes that helps. But it still got the access violation error.
The 32 bit version was not broken for me in the first place, so I don’t know what really was fixed. The back arrows on the Descendant View certainly were not fixed.
i get the AVE on 2 or more generations whether the person has a spouse and kids or not— usually happens within 1 or 2 clicks BUT some times it a little longer
We’ll need to test with your file, because the issue of crashing on the Descendant view was fixed on the files we had. Open a support ticket with a backup of the file and tell us which persons to test with.
Renee–I submitted a support ticket and database a little while ago for you to look at–as for persons to start with, it doesn’t seem to matter as long as you don’t start with my dad RIN 311 and Mom RIN 1 is not in the top spot–on either of these cases, it will run for a while ( not sure how long) BUT have noticed that after no error on this, I get an automatic AVE when I try to open another database
@thejerrybryan As Renee probably told you but just in case and to let everybody else know— the Fixed: Clicking arrows in descendant view w/ 2 generations could cause a crash was a very specific problem-- being the first child of the couple (3rd row) and clicking the right arrow would cause a crash (note-I had never experience this problem).
My problem --I was clicking on a left arrow on the first person ( to go to his father/ parents) and would get an AVE within 1 click…
So one down and more to go…
That was also my problem. I hope this is the last one.
@thejerrybryan I installed the latest update 10.0.9.0 for RM 10 and it appears that they did fix the problem of Access Violation Error that you and I were having of clicking on a left arrow on the first person ( to go to his father/ parents)..
I opened 6 databases in a row and had opened a couple of more and none of them caused an AVE–I didn’t run them for a long time but on all the previous versions, if it didn’t error out within a few clicks then it was okay except for getting a 217 error when I closed it–I didn’t get that either..
So Thanks Renee and everybody who made this happen–appreciate the help
1 Like
Yes, thanks to everybody who made this happen. I have now switched back to the 64-bit version of RM on Windows. I’m not willing yet to declare victory over all AVE errors, but the most severe and repeatable ones are fixed now.
I’m still getting the 217 error sometimes when I shutdown. I don’t really want to say much more about it until I can find a pattern where it is repeatable.