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.
Unfortunately the creater is not 'at hand' - any idea what the matter is?
Sounds like the files are corrupt. Were they sent as email attachments?
But I still can open and work on them - after the crash - like this:
open a file - ID freezes - forced close - and the it opens as it should -
And no, the wasn't send as email attachments. They were uploaded on an ftp-server...
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.
Correct. All saved and I've been working on them several times. Same procedure necessary.
Thanks for the advise - I'll try and trash the prefs ...
Just one other question - which pref-file to choose? And where to find it ...
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.
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?
Yes I guess I waited - but I made a test today... and waited a long time (ID - not answering) before making the forced close of ID -
The report is her: http://pastebin.com/VH0nqqvR
Den 30/04/2012 kl. 16.40 skrev John Hawkinson:
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...
That is ok - I will give it at try - and see what happens.
Thank you for your advice and support ..
Den 01/05/2012 kl. 14.40 skrev John Hawkinson:
I tried to switch off all non-system fonts - and now the document opened - and the ID froze. But actually it was a step further than before because i came as far as viewing the document .. I've put the report here:
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?
I'm not certain what you mean with Having the real crash report (from Send Signal: Abort) could you explain what I should do?
And yes there a 'document fonts' folder in the directory - but I have installed the fonts in the system.
I'm using apples 'font book' for management...
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.
Thanks a lot - now everything is OK ...
Have a nice day - mine certanly got much better right now
Den 02/05/2012 kl. 10.45 skrev Peter Spier:
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?
OK - sounds resonably... I don't have a fontmanager. I'm using apples 'font book' for managing ...
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.