After a complete reinstall of the app, updating the app, following their suggested (http://ancestry.custhelp.com/app/answers/detail/a_id/1370
), and various other system wide clean/fixes I can confirm there's still crashing in various portions of the application. Most of the time it's random, primarily though it happens on PDF exports of created books under the publish tab.
The random crashes have been reduced significantly however.
My exported PDF book is about 750 pages with no automated reports, charts, contents or indexes. Just individual reports and media files adding up to about 800mb total.
I can't export any type of book. PDF, RTF, DOCX, or export it as a PDF via the PRINT option. As well, once the book passes a certain size, I cannot split up the export (export pages 1 to 200, then 201 to 400, etc...). It still crashes.
No other apps are running and I show plenty of memory available while running the export via the activity monitor. The app runs up to about 4GB of memory used before it crashes. I've also noticed that FTM is only a 32-bit app suggesting it can only use 4GB max of memory, true? Does this not seem like a severe limitation for a database application?
IMPORTANT UPDATE: I just discovered that while FTM says it supports Mountain Lion, Mountain Lion is a 64bit only environment and Family Tree Maker is a 32bit only application. According to various threads around the internet most 32bit apps simply won't run and if they do become very unstable when running in a 64bit environment.