Search for content in message boards

Maximum Book Size via Publish Module?

Maximum Book Size via Publish Module?

Posted: 4 Mar 2013 5:07PM GMT
Classification: Query
Edited: 4 Mar 2013 5:33PM GMT
I'm running into crashes when exporting books via the Publish Module.

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?

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.

I'm using a 2012 MacBook Pro Retina with 16GB of memory on a fairly new and clean install of Mountain Lion 10.8.2.

If anyone can confirm they can't export books of a certain size, this would surely help! Thanks!

Re: Maximum Book Size via Publish Module?

Posted: 4 Mar 2013 8:00PM GMT
Classification: Query
In my experience the Publish section gets pretty iffy when the output is over about 250MB, at least on PDF. Sometimes you can export to RTF bigger than that but not always. However my usage is mostly limited to large individual reports, I've toyed with the Books section but not used it extensively.

While it's possible you're just hitting an unofficial size limit, do generate each report individually just to verify that you're not running into a data integrity error on one of the reports that's causing the crash.

Re: Maximum Book Size via Publish Module?

Posted: 4 Mar 2013 8:12PM GMT
Classification: Query
>>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.<<

I replied in the other thread on this too, but note that 32 bit APPLICATIONS run just fine on Mountain Lion. Many applications, including Google Chrome, are still 32-bit. What does not run is 32-bit KERNEL EXTENSIONS (utilities & drivers), and FTM does not supply any extensions.

You are correct that 32-bit applications can't address more than 4GB of virtual memory, and it's possible that this limitation is contributing to your issue. But a blanket statement that 32-bit apps shouldn't run on a 64-bit OS is false.

Re: Maximum Book Size via Publish Module?

Posted: 4 Mar 2013 8:27PM GMT
Classification: Query
Thanks Sean! Helps!

Re: Maximum Book Size via Publish Module?

Posted: 6 Mar 2013 5:41AM GMT
Classification: Query
Small update. In the crash log it states:

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

I'm no programmer, but this seems to be related to the app being 32bit vs 64bit environment. I realize you can run a 32bit in a 64bit but somewhere in there somethings screwy.
per page

Find a board about a specific topic