Skip navigation
Currently Being Moderated

Preflight crash, a cause and solution

Jun 2, 2011 4:46 PM

Ever since Live Preflight was introduced in CS4 we have had crashes with random documents that could only be fixed by deactivating Preflight. The problem has continued in CS5 and CS5.5.

 

The primary cause appeared to be importing Word files that have tracked changes. The solution to this is to accept all changes in Word before import the documents.

 

We still have older documents with this problem, and reimporting the word files is not an option. Saving as IDML does not fix the file. The following procedure appears to fix these files.

 

  1. Create an temporary text frame anywhere in the document
  2. From the Sub-Menu of the Track Changes panel, select Enable Tracking In All Stories
  3. Type a few characters
  4. From the Sub-Menu of the Track Changes panel, select Accept All Changes -> In This Document
  5. Delete the temporary text frame

 

Works with CS5.5. I no longer have CS4 installed to test this, so if you are having this problem with CS4, can you please test this solution and let us know.

 

If anyone want's to investigate the problem deeper, (hello Adobe) I can provide an InDesign file that will crash every time.

 

Note: Problem is on Mac, can't confirm if WIN is also affected.

 
Replies
  • John Hawkinson
    5,514 posts
    Jun 25, 2009
    Currently Being Moderated
    Jun 2, 2011 6:51 PM   in reply to ottopia

    Hi, ottopia.

     

    That's curious.

    Have you reported a bug?

    What's the crash report?

     

    I'm keenly interested in Live Preflight crashes because we have been fighting them in 7.0.4 (CS5) for quite some time.

    Ours frequently look like this (also Mac):

     

    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   ...esign.Package and Preflight      0x2ce7cb63 0x2cdd9000 + 670563
    1   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    2   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    3   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    4   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    5   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    6   ...esign.Package and Preflight      0x2ce7ced0 0x2cdd9000 + 671440
    7   ...esign.Package and Preflight      0x2ce7ce30 0x2cdd9000 + 671280
    8   ...esign.Package and Preflight      0x2ce78c17 0x2cdd9000 + 654359
    9   ...esign.Package and Preflight      0x2ce80699 0x2cdd9000 + 685721
    10  ...esign.Package and Preflight      0x2ced8cda GetPlugIn + 284170
    11  ...esign.Package and Preflight      0x2ced93fc GetPlugIn + 285996
    12  ...adobe.InDesign.AppFramework      0x2b53ffa7 GetPlugIn + 45687

     

    (Yes, we've been working on them with Adobe. No, we don't have a solution.)

     

    Ours don't have to do with Word documents, but may have to do with other kinds of links.

    Do you have Create Links When Placing Text And Spreadsheet Files checked? (I guess I'm not sure if that works with Word documents...)

     
    |
    Mark as:
  • John Hawkinson
    5,514 posts
    Jun 25, 2009
    Currently Being Moderated
    Jun 3, 2011 1:40 AM   in reply to ottopia
    I had submitted dozens of Adobe crash reports back when it first started in CS4 with no response. Finally gave up when the next few updates came out and it wasn't fixed

    Please note there's a hierarchy of getting bugs fixed in Adobe-land. Crash reports are at the absolute bottom, they are mostly only used as a research tool, where Adobe can look at them in an automated fashion and say, "The top 1000 crashes this month are..."; it's kind of needle-in-a-haystack thing.

     

    Next there are bug reports submitted at adobe.com/go/wish. These are probably a lot more likely to get fixed than crash reports, but that may not be saying very much.

     

    Then there are bug reports submitted via a case, through adobe.com/go/supportportal. You should be able to get a Bug Id number. hopefully then you'll have a real chance of getting the issue fixed.

     

    I'm sure there are further steps up the hierarchy that one could take after that, but I would be speculating.

     

    In any case, though, you should not expect that submitting crash reports is sufficient to get bugs fixed, just being pragmatic here.

     

    My report output looks pretty similar and create links for text files is not on. I ran an AppleScript on my test file to list any change items in the story, and there are none.

    Actually, it looks pretty different. The numbers do matter, and in your case the calls to the preflight module are interwoven with the calls to the UI module, which is interesting.

     

    Lucky that you're able to narrow your case down to a particular preflight. In our case that did not work. It sounds like you have a good reliably reproducible test document. That's great, you should provide it to Adobe (via the support mechanism) and hopefully you'll get it fixed in CS6!

     

    Thanks.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2011 6:31 AM   in reply to ottopia

    I've been fighting Prelight hangs with InDesign 7.5.1 on Windows 7 all morning. I don't have any imported Word files that are being tracked. I have to turn Live Preflight on, find the problem, turn it off, fix the problem, then turn it back on. Not terribly efficient. If left on ID will hang 100% of the time.

     
    |
    Mark as:
  • John Hawkinson
    5,514 posts
    Jun 25, 2009
    Currently Being Moderated
    May 11, 2012 10:15 AM   in reply to ottopia

    It's my understanding that 7.5.3 (a free upgrade to CS5.5) contains most of the preflight fixes that also made it into CS6. Have you found that not to be the case?

     
    |
    Mark as:
  • John Hawkinson
    5,514 posts
    Jun 25, 2009
    Currently Being Moderated
    May 13, 2012 9:10 PM   in reply to ottopia

    Ah. Does CS6 fix it?

     
    |
    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