Participant

Answered

Indesign quit or Out of memory when exporting or printing pdf.

Forum|Forum|14 years ago
February 4, 2012
4 replies
22222 views

Hi i have a mac Pro, 2x 2.26 GHZ Quad Core Intel- Xeon with 6GB 1066 MHz DDR3 running 10.6.8 and Adobe Design Premium.

when using Indesign and printing pdfs or exporting to pdf Indesign comes up with an "out of memory" or quits unexpectedly, please can someone explain why this would happen?

i have tested the ram/ reformated and reinstalled OSX 10.6.8 and Adobe but still this issue arises.

This topic has been closed for replies.

Correct answer tomaxxi

matthewvh wrote:
...when using Indesign and printing pdfs or exporting to pdf...

So, you are exporting/printing placed PDF-s from InDesign? From my experience, these crashes are caused by images/elements with extreme resolution inside those PDF-s. Best example is drop shadow which was scaled down, or big bitmap logo also scaled down extremely. These images/bitmaps usually are over 1000ppi, depending on original scale, and some of them are even higher. I had same experience few times and found few drop shadows inside PDF in over 5000ppi. After I resampled them to 300-600ppi, export/print went without any problem.

Hope that helps.

--

Marijan (tomaxxi)

http://tomaxxi.com

tomaxxiCorrect answer

Inspiring

matthewvh wrote:
...when using Indesign and printing pdfs or exporting to pdf...

So, you are exporting/printing placed PDF-s from InDesign? From my experience, these crashes are caused by images/elements with extreme resolution inside those PDF-s. Best example is drop shadow which was scaled down, or big bitmap logo also scaled down extremely. These images/bitmaps usually are over 1000ppi, depending on original scale, and some of them are even higher. I had same experience few times and found few drop shadows inside PDF in over 5000ppi. After I resampled them to 300-600ppi, export/print went without any problem.

Hope that helps.

--

Marijan (tomaxxi)

http://tomaxxi.com

Peter Spier

Community Expert

Out of Memory messages when processing PDF are not all that uncommon, unfortunately. I vaguely remember John having had something to say about it (besides considering it a bug) -- he's our resident Mac OS developer expert -- but for the life of me I can't remember what. You could try increasing the memory allocation or virtual memory for ID (sorry to be so vague, I'm a windows guy), but ultimately the usual advice when this happens is to see if the file will export in pieces, and if the entire thing will export that way, jsut combine them in Acrobat. If you find a particular page that won't export, even by itself, there's somthing onthat page that is causing the problem, so you need to remove objects until you isolate which one it is.

John Hawkinson

Inspiring

I probably said that it was a bug and not actually an out-of-memory condition.

In today's modern systems, it's really hard for software to make memory demands that are not easily achievable.

I think the key here is:

when using Indesign and printing pdfs or exporting to pdf Indesign comes up with an "out of memory" or quits unexpectedly, please can someone explain why this would happen?

Matthew, please upload the crash report from the "unexpected quit" to http://pastebin.com/ and post a link here for us to look at.

Something's clearly wrong. Presumably with one of your PDF files or perhaps your InDesign document. What patch level of InDesign are you using? Have you exported your document to IDML and re-opened it?

John Hawkinson

Inspiring

I suppose this only adds insult to injury, but too see a very similar output as above. My user is ready to scream. She probably already has, but since I am manning the helpdesk, I thought I would reach out to you folks here. I see a lot of the (error code=12) above and here. My user is running Mac G5 Intel, Indy CS4 6.0.6 and the devil is in the PDF export of an interactive PDF. We just added RAM as well. She has 8GB now with plenty of available hard drive space. How might I solve this problem, other than tell her it is in the Indy file(s)? I know she has tested and isolated, to no avail. I see this post is a month old - was there ever a resolution? Thank you.

3/12/12 2:57:41 PM [0x0-0x186186].com.adobe.InDesign[17674] Adobe InDesign CS4(17674,0xa086d720) malloc: *** mmap(size=2097152) failed (error code=12)

3/12/12 2:57:41 PM [0x0-0x186186].com.adobe.InDesign[17674] *** error: can't allocate region

3/12/12 2:57:41 PM [0x0-0x186186].com.adobe.InDesign[17674] *** set a breakpoint in malloc_error_break to debug

3/12/12 2:59:35 PM [0x0-0x186186].com.adobe.InDesign[17674] Adobe InDesign CS4(17674,0xa086d720) malloc: *** mmap(size=64000000) failed (error code=12)

3/12/12 2:59:35 PM [0x0-0x186186].com.adobe.InDesign[17674] *** error: can't allocate region

3/12/12 2:59:35 PM [0x0-0x186186].com.adobe.InDesign[17674] *** set a breakpoint in malloc_error_break to debug

3/12/12 3:05:37 PM [0x0-0x186186].com.adobe.InDesign[17674] Adobe InDesign CS4(17674,0xa086d720) malloc: *** mmap(size=16777216) failed (error code=12)

3/12/12 3:05:37 PM [0x0-0x186186].com.adobe.InDesign[17674] *** error: can't allocate region

3/12/12 3:05:37 PM [0x0-0x186186].com.adobe.InDesign[17674] *** set a breakpoint in malloc_error_break to debug

3/12/12 3:07:02 PM [0x0-0x186186].com.adobe.InDesign[17674] Adobe InDesign CS4(17674,0xa086d720) malloc: *** mmap(size=64000000) failed (error code=12)

3/12/12 3:07:02 PM [0x0-0x186186].com.adobe.InDesign[17674] *** error: can't allocate region

3/12/12 3:07:02 PM [0x0-0x186186].com.adobe.InDesign[17674] *** set a breakpoint in malloc_error_break to debug

3/12/12 3:08:41 PM com.apple.launchd[168] ([0x0-0x186186].com.adobe.InDesign[17674]) Exited abnormally: Bus error

smp-it:

My user is running Mac G5 Intel, Indy CS4 6.0.6 and the devil is in the PDF export of an interactive PDF. We just added RAM as well. She has 8GB now with plenty of available hard drive space. How might I solve this problem, other than tell her it is in the Indy file(s)? I know she has tested and isolated, to no avail. I see this post is a month old - was there ever a resolution?

Frankly, you should follow what I said on Feb. 5:

CS4? 6.0.6? That is two major revisions out of date. I suspect you would be much better off if you were using a current version of the software...

Upgrade to some reasonably modern hardware (Intel) and then upgrade to InDesign CS5.5 (though be mindful that CS6 should be announced in the next month or two, if Adobe sticks to expected schedules).

Also, remember that as a 32-bit app, InDesign can only address 4GB of RAM. So having 8GB will only help if you're running other apps at the same time as ID, it won't actually influence ID directly.

However, your output has one critical difference from the previously-posted output:

3/12/12 3:08:41 PM com.apple.launchd[168] ([0x0-0x186186].com.adobe.InDesign[17674]) Exited abnormally: Bus error

So, this indicates that InDesign ultimately crashed. A crash report should have been generated (See ~/Library/Logs/CrashReporter). Upload to http://pastebin.com/ and post a link here and we can take a look at it.

M

Michael_Gianino

Inspiring

You could try cleaning out your font cache.

A

Anonymous

have you tried trashing your preferences?