Are you running maintenance revsion 7.0.4?

What operating system?

Have you tried turning off Live Preflight?

Running the latest version.

Respectfully, this does not answer the question.

Many people make this statement and happen to be wrong

What is the precise 3-dotted version number reported by holding down Command and selecting About InDesign?

Moving the file out of the collected folder suggests the problem relates to opening a link. Not too surprising...

Depending on the version information I may have additional advice.

Thanks for clarifying (7.0.4.553)

With that in mind, when you experience a hang, there are two diagnostics you can gather that can help us determine why InDesign is hung,

both long files from Activity Monitor. So hang InDesign and start Activity Monitor.

1) Select InDesign, choose Sample Process, and save the file. Upload it to http://pastebin.com/ and post a link here.

2) Choose View > Send Signal: Abort (SIGABRT). This will force InDesign to crash, and generate a crash report. Upload the crash report to http://pastebin.com/ and post a link here.

Ashutosh's suggestion hypothesizes the problem is SING, Smart Independent Glyphlets. See http://helpx.adobe.com/indesign/kb/hang-freeze-open-create-file.html. It certainly could be, and his suggestion will do no harm otherwise.

With the above diagnostics we could certainly tell if the problem was SING, but there's not enough information to know at this point.

jfreestern wrote:

 

Did try one thing that kind of works -- moved the ID file out of the collected folder and that seems to work.

This suggests to me that the problem may be realted to a linked file, but you should run John's suggested diagnostics to verify.

Do you have any Font management software installed?

Well, we're guessing. but it's a font-related BUG.

Bugs are tricky things. Their behavior can change depending on the precise path that they are approached from.

Perhaps ID treats opening a new document a little differently than crash-recovering a document and the problem fails to manifest...perhaps there is an ordering dependency?

It's definitely a bug. What is triggering it is hard to say. I suspect a corrupt font, but I could be wrong.

Certainly not everything in your story lines up perfectly with that theory...

jfreestern wrote:

 

Although wouldn't they be the same as the ones loading from Suitcase Fusion? -- that is, if InDesign is trying to load the fonts from the packaged font folder when the ID file is in the folder, what fonts is the file using when the file is outside the folder (those already loaded in Fusion)? and if it's the Fusion fonts, they would in theory be the same fonts that ID collected and packaged, yes?

I wouldn't swear to it, but I think Suitcase would be entirely bypassed in this case. I know, for instance, that ID uses the Document Fonts rather than the installed versions if both are present.

Also just for clarification, when a job is packaged from ID and the fonts that are being used are loaded through Suitcase, when ID collects the fonts, isn't it pulling them from Suitcase's database (I have all my fonts in the Suitcase Fusion database)?

Essentially yes, if indeed the job is packaged on the same machine with the same configuration as the machine where it is later opened. That may be the case in your situation, but it is not necessarily generally true.

And for clarity, to be technical, ID is not pulling the fonts from Suitcase's database

ID takes the fonts from the OS. Suitcase provides them to the OS. So there is a level of indirection involved, and that indirection may reflect the opportunity for bugs in the OS and bugs in Suitcase and bugs in InDesign to all interact in new (or old) and exciting (always) ways.

If yes, then they should be one and the same fonts -- that is the ones in the collected fonts folder should be the same as the ones in my suitcase database unless some damage is occuring during collection -- correct? (Also, all the fonts used in the booklet are fonts that I had previously installed in Suitcase (none were sent to me by others)--unless an embedded font in a PDF that I placed into the document could be causing an issue or conflict with my fonts??

So, yes, it sounds like they should be the same fonts. And that certainly begs the question why it would be different if ID loads a font from Document Fonts versus Suitcase loading a font through the OS mechanism. But certainly they are different mechanisms and may have different bugs.

Peter wrote:

I wouldn't swear to it, but I think Suitcase would be entirely bypassed in this case. I know, for instance, that ID uses the Document Fonts rather than the installed versions if both are present.

Well, Suitcase installs a hook that gets triggered when ID loads a document--this is autoactivation. It causes Suitcase to stop and load fonts when the document is opened. At which point it could do anything... Only then, after Suitcase does whatever it does (with auto-activation enabled, only, of course), then ID will do what it does (either loading from the OS or loading from Document Fonts).

Plenty of room for all sorts of problems...

jfreestern wrote at Apr 26, 2012 9:48 AM:

Good explanations and I agree lots of room for problems. Will give things a try a bit later.

Any updates?