Adobe Community: InDesign CS6 crashes during PDF export

amartindesign Calculating status...

Currently Being Moderated

InDesign CS6 crashes during PDF export

May 31, 2012 1:06 PM

Tags: #pdf #mac #export #indesign #cs6 #crash_when_exporting

I have been attempting to export a magazine design to PDF using the dialogue in InDesign CS6 (for Mac). The PDF gets to around 90% in the background tasks panel and crashes every time. I have removed preferences, reinstalled InDesign, upgraded to Suitcase Fusion 4 and am still having problems. I have even tried printing as a .ps file and it crashes during that as well. A few weeks ago I had a similar problem but found that I was opening CS5 .indd files and not resaving them as CS6 .indd files before exporting. Once I resaved/renamed them in CS6 it appeared to fix the problem. Now I can't seem to fix this one. I have exported other files and it works fine. I even packaged the .idml file and a colleague of mine opened it up in CS5.5 and was able to export it. I thought it might have something to do with corrupt fonts but I disabled all fonts and still couldn't get it to export. Any help or advice would be much appreciated as I am on a deadline. Here is the code from my latest crash report: http://pastebin.com/mRCLsYti

19572 Views 54 Replies Latest reply: April_W, Jan 10, 2013 10:23 AM

Replies 1 2 Previous Next

Currently Being Moderated

1. amartindesign,

May 31, 2012 1:37 PM in reply to amartindesign

Report

Appears to have something to do with this thread but I have no clue what is going on here...

Thread 32 Crashed:
0   libsystem_kernel.dylib              0x93ad89c6 __pthread_kill + 10
1   libsystem_c.dylib                   0x91240f78 pthread_kill + 106
2   libsystem_c.dylib                   0x91231ce3 __abort + 198
3   libsystem_c.dylib                   0x9122e64a __stack_chk_fail + 253
4   com.adobe.CoolType                  0x010137c9 CTInit + 1626733
5   com.adobe.CoolType                  0x01014053 CTInit + 1628919
6   com.adobe.CoolType                  0x010111ba CTInit + 1616990
7   com.adobe.CoolType                  0x0100f77e CTInit + 1610274
8   com.adobe.CoolType                  0x00f6478e CTInit + 909874
9   com.adobe.CoolType                  0x00ef40a2 CTInit + 449350
10 com.adobe.CoolType                  0x00e726ba 0xe1e000 + 345786
11 com.adobe.PDFL                      0x2cc792e2 PDFontPSFlushIncrGlyphList + 85285
12 com.adobe.PDFL                      0x2d08e898 PDEFontGetWidthsNow + 8752
13 com.adobe.PDFL                      0x2d08ebb9 PDEFontGetWidthsNow + 9553
14 com.adobe.PDFL                      0x2d08fb13 PDEFontGetWidthsNow + 13483
15 com.adobe.PDFL                      0x2d0909a1 PDEFontGetWidthsNow + 17209
16 com.adobe.PDFPort                   0x187ffffe PDFPortInitialize + 560298
17 com.adobe.PDFPort                   0x18800375 PDFPortInitialize + 561185
18 com.adobe.PDFPort                   0x187e88f0 PDFPortInitialize + 464284
19 com.adobe.InDesign.PDF              0x1851cf09 0x184e7000 + 220937
20 com.adobe.InDesign.PDF              0x1854064d GetPlugIn + 66509
21 com.adobe.InDesign.PDF              0x185430b8 GetPlugIn + 77368
22 com.adobe.InDesign.PDF              0x1852abb5 0x184e7000 + 277429
23 PublicLib.dylib                     0x01701d7c Command::DoImmediate(short) + 62
24 com.adobe.InDesign.Utilities        0x121ce691 0x121ca000 + 18065
25 com.adobe.InDesign.Utilities        0x121ce8a0 0x121ca000 + 18592
26 com.adobe.InDesign.AppFramework     0x10c2cbba 0x10c10000 + 117690
27 PublicLib.dylib                     0x01702724 CmdUtils::ProcessCommand(ICommand*) + 48
28 com.adobe.InDesign.PDF              0x1866abb6 GetPlugIn + 1288502
29 com.adobe.InDesign.PDF              0x1866ef47 GetPlugIn + 1305799
30 com.adobe.InDesign.AppFramework     0x10d0a749 GetPlugIn + 852745
31 com.adobe.InDesign.AppFramework     0x10d0bca6 GetPlugIn + 858214
32 com.adobe.InDesign.AppFramework     0x10d0c804 GetPlugIn + 861124
33 com.adobe.InDesign.AppFramework     0x10d0d3c5 GetPlugIn + 864133
34 com.adobe.InDesign.AppFramework     0x10d0e98e GetPlugIn + 869710
35 com.adobe.InDesign.AppFramework     0x10d0e9fa GetPlugIn + 869818
36 com.adobe.InDesign.AppFramework     0x10d0ea66 GetPlugIn + 869926
37 com.adobe.boost_threads.framework   0x01c6a40d thread_proxy + 141
38 libsystem_c.dylib                   0x9123eed9 _pthread_start + 335
39 libsystem_c.dylib                   0x912426de thread_start + 34

|
Mark as:
Currently Being Moderated

2. Larry G. Schneider,

May 31, 2012 3:22 PM in reply to amartindesign

Report

My best guess would be a bad font but I have nothing concrete to back it up.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

3. John Hawkinson,

May 31, 2012 3:35 PM in reply to Larry G. Schneider

Report

Yeah, I'd agree. CoolType is a font rendering technology. Remove all non-system fonts, try again...

|
Mark as:
Currently Being Moderated

4. amartindesign,

May 31, 2012 3:49 PM in reply to John Hawkinson

Report

I deactivated all fonts and attempted to export directly from InDesign and it crashed again. However, this time when I also tried to print to .ps and selected download "none" in the Graphics/Fonts dialogue box, the postscript saved and it worked flawlessly making the PDF in Distiller.

|
Mark as:
Currently Being Moderated

5. Scott Worthington,

May 31, 2012 4:29 PM in reply to amartindesign

Report

Does removing the suitcase plugin from the Plugins folder change any of the behavior?

|
Mark as:
Currently Being Moderated

6. amartindesign,

May 31, 2012 4:50 PM in reply to Scott Worthington

Report

There is no plugin installed at the moment. After updating to Suitcase Fusion 4 today there wasn't one installed by default.

|
Mark as:
Currently Being Moderated

7. Scott Worthington,

May 31, 2012 4:58 PM in reply to amartindesign

Report

How does it behave in safeboot? http://support.apple.com/kb/HT1455

|
Mark as:
Currently Being Moderated

8. amartindesign,

May 31, 2012 5:29 PM in reply to Scott Worthington

Report

Just tried safe mode. It crashed at 95% progress like it has been doing all along. On a positive note, I was able to make a PDF from Distiller by going the .ps route.

|
Mark as:
Currently Being Moderated

9. amartindesign,

May 31, 2012 5:37 PM in reply to amartindesign

Report

The weird part though was I made the PDF from Distiller I selected to save it in spreads and it ended up ignoring that and saving it in single pages.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

10. John Hawkinson,

May 31, 2012 6:18 PM in reply to amartindesign

Report

Hmm.

I deactivated all fonts and attempted to export directly from InDesign and it crashed again. However, this time when I also tried to print to .ps and selected download "none" in the Graphics/Fonts dialogue box, the postscript saved and it worked flawlessly making the PDF in Distiller.
Well, if you deactivated "all fonts," then why didn't you have a problem when you produced the PDF? Are you sure the problem isn't one of the fonts you're using in the document? Do you have fonts in a Document Fonts folder, also?

|
Mark as:
Currently Being Moderated

11. amartindesign,

May 31, 2012 6:29 PM in reply to John Hawkinson

Report

Actually that might have something to do with it. Each issue of this magazine I package and save the fonts in that issue's folder. Then I typically open an older issue, delete the content and resave as a new issue as I'm working on it. Going to try deleting all of those Document Fonts folders and see what happens.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

12. John Hawkinson,

May 31, 2012 6:30 PM in reply to amartindesign

Report

Well, easier to rename the folder rather than delete it...

|
Mark as:
Currently Being Moderated

13. amartindesign,

May 31, 2012 6:32 PM in reply to John Hawkinson

Report

Trashed those folders and this time it got to 97% instead of 95% before crashing lol. When I mentioned deactivating the fonts, I went into Suitcase Fusion 4 and turned them off. Also, for what it's worth, I noticed when I package the file in the preflight stage there are a ton of fonts embedded that I'm not actually using in the document.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

14. John Hawkinson,

May 31, 2012 6:35 PM in reply to amartindesign

Report

Please actually remove the plugin from /Applications/Adobe InDesign CS6/Plugins

|
Mark as:
Currently Being Moderated

15. amartindesign,

May 31, 2012 6:42 PM in reply to John Hawkinson

Report

Actually I think those embedded fonts are in the ads. As for the plugin, this is what I see in the /Adobe InDesign CS6/Plugins folder...

/Data Services
/Dictionaries
/Filters
/Graphics
/InCopyWorkflow
/Interactive
/Layout
/Page Item
/PMPack
/Prepress
/Sandbox
/Script
/Tables
/Text
/UI
/Utility
/Workflow
/Workgroup
/XMedia

Which one of those should I remove?

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

16. John Hawkinson,

May 31, 2012 6:54 PM in reply to amartindesign

Report

Those are all folders...
but usually the autoactivation plugin is installed in the Font Activation/
folder. Maybe you don't have it installed though...I guess that's esp.
plausible since CS6 came out recently and the older version would
not have been compatible, and I don't know if you have (or if Extensis even ships!) a CS6 version.

Well, if it's a corrupt font in an ad, well... Delete half the pages,
export, see if you find the problem. Lather rinse repeat...
Do this work on a copyof your file of course.

|
Mark as:
Currently Being Moderated

17. amartindesign,

May 31, 2012 7:32 PM in reply to John Hawkinson

Report

Just read on the Extensis forums that there is no plugin yet for CS6. If I sent the packaged files to a colleague who then exported a PDF from CS5.5 no problem, wouldn't that already rule out corrupted fonts or fonts in ads?

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

18. John Hawkinson,

May 31, 2012 7:43 PM in reply to amartindesign

Report

Well, yes and no.
Perhaps we have a subtle form of corruption that only CS6 is sensitive to?
Or perhaps one of the problem fonts is a system font on your system.

It would be best if you sent it to a colleague with CS6 and CS5.5 and that person were to determine whether they had differential results between the two.

I would really start divide-and-conquer on your document.

Just to be clear, you have a workable solution so you're not up against tight deadline pressure anymore, correct?

|
Mark as:
Currently Being Moderated

19. amartindesign,

May 31, 2012 8:04 PM in reply to John Hawkinson

Report

re: workable solution — Well kind of. I can save as a .ps but when I distill it the PDF doesn't save in spreads or with any other settings I mark (i.e. bleeds, crop marks, etc.). I have to upload to the printer Tuesday so hopefully I can get to the bottom of it by then. By the way, I opened up a couple of other issues and they have all crashed as well with the exception of one. Now to experiment with taking the file apart.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

20. John Hawkinson,

May 31, 2012 9:36 PM in reply to amartindesign

Report

It's rather strange that you want it in spreads. Are you sure your printer wants that?
Anyhow, you should be able to add crop marks in Acrobat.

|
Mark as:
Currently Being Moderated

21. amartindesign,

May 31, 2012 9:43 PM in reply to John Hawkinson

Report

No actually when I send it to the printer it will be in individual pages and each page will be it's own individual PDF labeled accordingly. I just like to show my client the PDF proofs in spreads.

|
Mark as:
Currently Being Moderated

22. Laubender,

Jun 1, 2012 8:15 AM in reply to amartindesign

Report

To show client spread view with PDF of single pages, you could change the "Layout View" in Acrobat Pro. Go to "Document Properties", "Initial View" and choose "Two-Up (Cover Page)" in "Layout View". Then save the document. Your client should open the file in Adobe Reader 8 (?) and above…

Don't do that with an PDF/X; otherwise you will break the /X-specifications.

Uwe

|
Mark as:
Currently Being Moderated

23. amartindesign,

Jun 1, 2012 11:59 AM in reply to John Hawkinson

Report

Ok, so I recently read in the Extensis best font management practices PDF about moving all of my /Library/Fonts; Home/Library/Fonts and ApplicationSupport/Adobe/Fonts to a centralized location with my other fonts. I have since done this and now have full control over every font on my system (with the exception of the System/Fonts as I didn't move those) in Suitcase Fusion. I disabled every single font on my computer and the PDF export is still crashing based on this "Adobe CoolType" thread. I've about exausted all of my options as last night I even removed every single Adobe file from my computer (had some old stuff floating around from CS3 days) and reinstalled the entire CS6. No luck still.

|
Mark as:
Currently Being Moderated

24. Peter Spier,

Jun 1, 2012 12:07 PM in reply to amartindesign

Report

What verion of Suitcase are you using? Do you have the latest patch?

I think you said there was no plugin yet for CS6, but it would be worth your while to make sure there is nothing from Extensis in your plugins folders.

|
Mark as:
Currently Being Moderated

25. amartindesign,

Jun 1, 2012 1:15 PM in reply to amartindesign

Report

Just got off the phone with Adobe. Had supurb customer service by the way. Anyhow, while on the phone with them I made individual PDFs of each page, trying to see which one was causing the crash. Turned out to be on page 41 of a 46 page magazine. An ad had become corrupted. I looked in Adobe Bridge and it appears that ad was created in Quark. Go figure. Anyhow, it's all solved now. Thanks for everyone's help.

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

26. John Hawkinson,

Jun 1, 2012 4:35 PM in reply to amartindesign

Report

Well, hopefully you won't let them off the hook. I mean, a corrupt PDF shouldn't crash ID, it should detect it and tell you what happened.
Anyhow, glad you got there. I feel dumb for not suggesting you create PDFs of subsets of your document (go by halves), though it should have been equivalent to deleting half the pages (though a bit faster).

Have a great weekend.

|
Mark as:
Currently Being Moderated

27. amartindesign,

Jun 1, 2012 5:25 PM in reply to John Hawkinson

Report

Haha yea probably shouldn't have let them off that easy but after the stress I've been the under the last 48 hours having it export flawlessly made me happy . By the way I noticed here that someone was having similar problems with InDesign (CS4) crashing due to a placed PDF originally created in Quark. When I open the previous issues of this particular magazine, that same company's ad (sometimes it's a full page and sometimes a half page) has been causing it to crash as well (although it did not do this in CS5). Weird. Might need to have that guy send me his ads as high-res TIF files from now on. Have a good weekend as well.

|
Mark as:
Currently Being Moderated

28. Andrew Burwell,

Jun 17, 2012 6:35 PM in reply to amartindesign

Report

I'm having the exact same problems in CS6, it dies every time trying to export a magazine at 97%. Guess I'll try one page at a time to see where it's dying.

|
Mark as:
Currently Being Moderated

29. Andrew Burwell,

Jun 17, 2012 6:57 PM in reply to Andrew Burwell

Report

Turned out my issue was also a bad PDF ad.

|
Mark as:
Currently Being Moderated

30. amartindesign,

Jun 17, 2012 7:40 PM in reply to Andrew Burwell

Report

Glad you got your issue resolved. Did you happen to see in Bridge if that PDF was created with Quark? Just curious as I feel like that might have been the issue as another issue of the magazine I was working on had the same issue and it was a different ad but made by the same company in Quark.

|
Mark as:
Currently Being Moderated

31. Encryptics-Graphcs,

Jun 21, 2012 9:04 AM in reply to amartindesign

Report

I'm having crashes, multiple, and can't see to get a PDF no matter what I do. Adobe Presets crash, export crashes, Printing crashes, etc.
It appears that when a "warning" windows tries to open, like when you're packaging and it says "warning, something something something is kinda wrong", it crashed.
EVERY FREAKIN TIME!
I'm on Lion, but this doesn't seem like an easy work around.

Discuss...

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

32. John Hawkinson,

Jun 21, 2012 9:08 AM in reply to Encryptics-Graphcs

Report

Encryptics-Graphcs wrote:

I'm having crashes, multiple, and can't see to get a PDF no matter what I do. Adobe Presets crash, export crashes, Printing crashes, etc.
Post a crash report to http://pastebin.com/ and post a link here.

|
Mark as:
Currently Being Moderated

33. Encryptics-Graphcs,

Jun 21, 2012 9:16 AM in reply to John Hawkinson

Report

Thank you, I can do that.

http://pastebin.com/embed_iframe.php?i=E1yj2XF4

|
Mark as:
5,528 posts
Jun 25, 2009

Currently Being Moderated

34. John Hawkinson,

Jun 21, 2012 9:32 AM in reply to Encryptics-Graphcs

Report

Unfortunately the stack in the crash report is corrupt and useless:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0xac494630 _XHNDL_trapback_instruction + 0
1 ??? 0xffffffff 0 + 4294967295

Has this ever worked? I would try a reinstall.

|
Mark as:
Currently Being Moderated

35. Peter Spier,

Jun 21, 2012 9:37 AM in reply to John Hawkinson

Report

There's another thread about crashing and warning dialogs at http://forums.adobe.com/message/4510734 that seems to suggest there's a bug and offers a possible way to get your work done.

|
Mark as:
Currently Being Moderated

36. Encryptics-Graphcs,

Jun 21, 2012 11:53 AM in reply to Peter Spier

Report

That helped with the page removal.

The crashes are still there on a reinstall. I downloaded the suite though, so I'm redownloading it to see if that is the issue.

|
Mark as:
Currently Being Moderated

37. Marijan Tompa,

Jun 21, 2012 12:22 PM in reply to Encryptics-Graphcs

Report

Have you tired disabling background export? Here is how to do it:
http://indesignsecrets.com/a-new-workaround-for-that-pesky-background- export-issue.php

Or download script from here:
http://tomaxxi.com/downloads/
and scroll down to "Control Background Export".

Hope that helps.

--
Marijan (tomaxxi)
http://tomaxxi.com

|
Mark as:
Currently Being Moderated

38. Todd H&M,

Jun 22, 2012 10:18 AM in reply to Marijan Tompa

Report

I'm also not able to create PDF files from the new CS6 InDesign. Also not able to create a package. Both cases crash InDesign.

|
Mark as:
Currently Being Moderated

39. Encryptics-Graphcs,

Jun 22, 2012 10:33 AM in reply to Todd H&M

Report

HERE'S what I have figured out from talking to tech support:
(I'm on a Mac)
- First, close all apps, and REBOOT. I know, I'm just telling you what I did.
- From the "finder" menus at the top, choose "GO" and hold down the "Option" key to choose the "Library" folder.
- Next, go into the "Preferences" folder...
- Then into the "Adobe InDesign" folder.
- Copy the version (8) folder to your desktop.
- Now, open up InDesign, create a new doc., and see if it goes to PDF.

I figured out that if ANYTHING was RGB, or gives InDesign a reason to show you a "warning" window, it will crash. I had to alter some files, and even save them down to CS5 settings so they'd stop causing issues.
Eventually I got it to work.

Adobe REALLY needs to remedy this, I don't understand how they can release a brand new version where a program crashes like this. I'm disappointed, and wish my employer hadn't purchased this version. 5(.5) was fine.
Adobe, fix it.

|
Mark as: