I’m not totally sure if it started with 9.1.4 or 9.1.6, but up to the latest 10.0.1 I see frequent RM shutdowns (no error message, just quit) with TreeShare connected databases. This is on a Mac with latest OS (Sonoma), may happen on Windows too but I don’t do any Treeshare activity when using RM on Windows.
If I have a tree that’s not connected to Ancestry I can have that database open for hours and absolutely nothing will happen. If I have a database connected to Ancestry RM will simply shut down if the session with Ancestry is idle for any period of time. It appears to be related to the new OAUTH functionality, but it didn’t start until recently.
Relatively simple for me to recreate. Open a TreeShare connected DB, log into Ancestry via Publish, do some Ancestry stuff, go do something else for a while (maybe 5 minutes) that doesn’t involve Ancestry (even some offline research) then attempt to do something else with Ancestry such as hints or TreeShare. Boom, RM quits.
It doesn’t appear to have anything to do with a corrupted database as all the database tools work without issue, and even SQLite Pro verification is clean. All changes up to the one being attempted at shutdown are saved.
Has anyone else seen this? Obviously the database in question may be the exception from a Treeshare standpoint, as it’s 25,000+ that is pretty much fully in sync.
I’m also using RM 10.0.1, running under Mac OS 14.6.1, and I think I’m seeing the same thing happening -I just hadn’t made the connection with TreeShare. I’ll need to check, following your procedure to the letter, to confirm that the circumstances are identical, but what you describe sounds awfully familiar. My database has about 22,500 individuals.
Thanks Renee, I have not opened a ticket because I want to make sure I can accurately describe how to reproduce the problem. The databases from me you already have should work for testing.
First step in checking process completed. I spent about 2 hours working on my database yesterday, without connecting to Ancestry. The work I was doing was mostly upgrading/correcting citations. There were no shutdowns. I connected to Ancestry and ran TreeShare before closing RM - again, no problems.
Today I intend repeating the process, doing the same sort of work, but with the Ancestry connection open. Iy will be interesting to see what happens
I have an M1 Mac running the latest OS and the latest RM. I repeatedly and randomly have RM crashes when I am using the Ancestry tree feature. I reported it through the chat function. I wonder if a cache or buffer fills up as you sync individuals in the trees, and causes a crash when it fills up. They told me to quit using Safari and switch to using Chrome as a browser. They also told me that I was the only one having a problem with crashes and that the problem was probably on Ancestry’s side. I will say that setting the default browser to Chrome instead of Safari did reduce the number of crashes when using Ancestry. I still had 3 crashes today in a 2 hour session.
It may be unrelated to the crashes, but the other thing that I have noticed while syncing between Ancestry and RM10 on my Mac, is that after I do/accept a number of changes, it looks like I have a few (not everyone) duplicate people on the RM side of the table. If I close the sync feature and look for the duplicates, they are not there, which is always a relief!
@keithcstone - good catch. Can confirm the same “intermittent and unexpected quit” behavior - running on M1 pro mac w/ 14.6.1 sw - though I have a much smaller db - under 1k. All my dbs are connected to ancestry (I also occasionally use the Familysearch API ). I don’t connect to ancestry every session and will pay more attention to treeshare’s logged in status the next time it happens.
[edit: I am fairly confident that this happens when I am not accessing the Ancestry treeshare screen. Recently I have been cleaning up webhints; have mostly been focusing on findmypast.]