Search for content in message boards

Crashes

Posted: 25 Nov 2010 10:25PM GMT
Classification: Query
I'm experiencing lots of crashes with the new Family Tree Maker 2010 for Mac. I'm working on a database of 542 individuals, the file size is about 831KB, and 165 media items. I've been trying to compact it, but it crashes everytime I try that. I'm using it on a MacBook Pro with Mac OSX. The program has been working well until last night. It crashes when trying to merge with my tree on Ancestry, crashes when entering in a source, crashes while attaching media. Not sure what I'm doing wrong.

Re: Crashes

Posted: 26 Nov 2010 4:30AM GMT
Classification: Query
I don't think you are doing anything wrong. I am having the same problem. I compacted once, but it has been crashing in the process ever since. I have runs of using the software with no crashes, but more often it hangs when merging then crashes. I think that there is a serious bug that desperately needs a fix. I've never seen Mac software that crashes as often.

Re: Crashes

Posted: 26 Nov 2010 11:48AM GMT
Classification: Query
I would suggest the following for the moment.

1. If you only have 4GB of memory don't run any other programs at the same time.

2. You quit and restart every 30 minutes.

3. If you want to merge from Public Trees, type the details in instead. Allows a more critical approach immediately to the data.

4. If you are merging a gedcom, use the append only option and then manually merge the hopefully only one or two individuals who are duplicated.
Posted: 4 Dec 2010 5:20PM GMT
Classification: Query
I'me having the same problem. Good to know that it is not just me. Keeps crashing and also locks up when I try to compact. Hopefully they will fix the bug soon!!

Re: Crashes

Posted: 4 Dec 2010 7:33PM GMT
Classification: Query
I think my problem may be different, but for what it's worth... I've had no problem with crashes until recently but I think I've found the problem.


I'm using DropBox to store the DB so that I can use FTM on both my MBP and iMac (both running OSX 10.6/5). It makes no sense to me to store backups in the same folder as the main file so I changed Prefs to store backups in the regular Document folder on each computer. Apparently FTM doesn't like that, at least when one is using Dropbox.


I changed the Prefs back to FTM's default backup and things seem to have calmed down. I don't think Dropbox itself is the problem because I also use it for my Reunion and 1Password databases without issue. For my system, at least, FTM seems to want that last backup in the same folder as the main DB.

For anyone who hasn't tried Dropbox, I can't recommend it highly enough!!! You get 2 GB free storage; my husband and I were so happy with it that we both paid for the 50 GB plan. DropBox gives both users extra free space if a referral link is used. If you give it a try and are so inclined, I would love to have my link used: https://www.dropbox.com/referrals/NTcxMjA4MjA5?src=global0

Re: Crashes

Posted: 4 Dec 2010 8:22PM GMT
Classification: Query
I have the same set up as you.

My FTMM file goes to the default Family Tree Maker folder in documents, as do the autobackups. At the end of a session on a particular machine I then copy everything across to the Dropbox folder and then when I switch on the other machine do the reverse.

I am not comfortable with storing a file on which I am working in the DB folder, whether it causes crashes or not. Whilst this may have caused crashes, there is regardless a memory management problem with the program.

Re: Crashes

Posted: 4 Dec 2010 9:51PM GMT
Classification: Query
Thanks so much for this post, Tony. I didn't even think about doing it that way but will definitely follow your lead right this minute. I agree completely about storing backups in the same folder as the original file--what's the point? ;-}

Re: Crashes

Posted: 4 Dec 2010 9:54PM GMT
Classification: Query
PS-I also agree about the memory problems, Tony. A Mac application shouldn't require quitting and saving every half hour and it certainly shouldn't require shutting down all other programs.

Re: Crashes

Posted: 6 Dec 2010 12:02AM GMT
Classification: Query
I ended exporting my file as a Gedcom, and then importing that into FTM. Then I trashed the old file. This time, I just did not merge with anything from Ancestry, especially census files or anything that merged with an image. It's been working perfectly so far. But still, a shame that I cannot link to any images.

Re: Crashes

Posted: 6 Dec 2010 3:39AM GMT
Classification: Query
I've been using Apple computers and Macs for as long as they've been around. This is exactly the reason I'm always reluctant to buy software that was originally written for Windows. I know the publisher says this was written from the ground up for Mac, but I'm having a hard time believing that. (Well, unless PC users also get constant crashes!)

I really like this program's format and would love to use it as my main application. For now, though, I'm playing with it and keeping my real database in Reunion. Too bad FTMM was released with so many bugs.
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | New Privacy | New Terms and Conditions