Skip navigation
Currently Being Moderated

ID crashing when opening document in 5.0, converted from 5.5

Apr 30, 2012 2:41 AM

Tags: #cs5 #mac #indesign

I have 6 documents which I got as IDML-files.

They are originally made in 5.5 - I'm using 5.0. Working on a mac (OSX 10.6.8)

When opening a document ID freezes. Then I make a forced close down - and start ID again. And then the document is opened and I can work on it.

This happens with 5 of the documents - the 6th opens without problems.

Any suggestions on what to do?

 
Replies
  • Currently Being Moderated
    Feb 21, 2013 9:18 AM   in reply to TeR-D

    I'd ask the sender to recreate the files and resend them. It wouldn't be a half bad idea to upgrade to 5.5, either.

     

    If you do so by May 6 you'll get CS6 for free.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 30, 2012 4:56 AM   in reply to TeR-D

    Sounds like the files are corrupt. Were they sent as email attachments?

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 30, 2012 5:22 AM   in reply to TeR-D

    And this continues to happen after they’re saved as CS5 documents?

     

     

     

    Perhaps it’s ID that’s gone a bit wonky. Try trashing your prefs.

     

     

     

    Bob

     
    |
    Mark as:
  • John Hawkinson
    5,527 posts
    Jun 25, 2009
    Currently Being Moderated
    Apr 30, 2012 6:48 AM   in reply to TeR-D

    See

    Troubleshooting 101: Replace, or "trash" your InDesign preferences.

     

    Also, we can debug your hangs.

    Run Activity Monitor and select InDesign.

    Choose Sample Process. Save the file and upload to http://pastebin.com/.

    Then go to View >Send Signal: Abort (SIGABRT) and force the program to crash.

    You'll get a crash report.  Also upload that to pastebin.

     

    Post the pastebin link here. We'll look at it and tell you what ID is doing when it hangs.

     
    |
    Mark as:
  • John Hawkinson
    5,527 posts
    Jun 25, 2009
    Currently Being Moderated
    Apr 30, 2012 7:40 AM   in reply to TeR-D

    TeR: Please suppress your signature and personal information from your replies. They are public on the Internet for all to see! (Also, removing the quoted text is helpful too).

     

    The data you provided looks like a normally functioning InDesign. Did you wait for it to freeze before collecting the data?

     
    |
    Mark as:
  • John Hawkinson
    5,527 posts
    Jun 25, 2009
    Currently Being Moderated
    May 1, 2012 5:40 AM   in reply to TeR-D

    OK, this hang report does show a problem; it's not quite as definitive

    as the two reports I asked for initially, but it shows InDesign

    stuck in the font manager.

     

    This is consistent with a damaged or corrupt font (or something else

    about the font that confuses InDesign).

     

    Assuming you can reproduce this problem, the general answere is to

    remove all non-system fonts and add them back in by halves (divide and

    conquer) until you find the source of the problem. I realize this may

    take a while...

     
    |
    Mark as:
  • John Hawkinson
    5,527 posts
    Jun 25, 2009
    Currently Being Moderated
    May 1, 2012 7:49 AM   in reply to TeR-D

    That looks like the same font problem. Having the real crash report (from Send Signal: Abort) would be more clear though.

    Do you have a Document Fonts folder in the directory with the IDML files?

    Do you have some 3rd party font management tool that might be adding fonts?

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 1:45 AM   in reply to TeR-D

    If there is a Document Fonts folder present with the .indd or .idml file ID will use the fonts in that folder for the document regardless of whether the same fonts are installed on your system. We had another user this week who encountered some problems with fonts in a document fonts folder, so try moving or renaming the fonts folder and see what happens.

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 2:00 AM   in reply to TeR-D

    That means either one of the fonts in that folder is bad, or perhaps there's some sort of conflict being caused by trying to load the font twice. Do you have a font manager?

     
    |
    Mark as:
  • Currently Being Moderated
    May 2, 2012 2:18 AM   in reply to TeR-D

    Try moving half of the fonts out of the Document Fonts folder (put them in a new folder) and put the fonts folder back so ID sees it, then try opeing the file again. If it crashes, remove half of the remaining fonts and try again. If it doesn't crash, put half of the removed fonts back and try again. You should be able to isolate a bad font, if there is only one, in very short order.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points