Can you maybe provide more details as to:
- What version of InDesign you are using (is this only CS 3-4) ?
- Is this with all documents?
- Are these documents coming from older versions of InDesign?
- What happens if you export to IDML and then open that IDML back in InDesign?
Alternatively, if InDesign crashes, you can retrieve the application crash log from your system and call up Support so somebody can look into this for you,
- I am using Adobe InDesign CC 2015
- It appears to be with all documents
- It does happen when creating an entirely new document
- If exported to IDML and re-opening, it still occurs
reading your answers, it does look like it could be a bug.
You need to get in touch with Support so someone can help you retrieve the log files and report this to the product team.
I've been having this problem ever since the column span was introduced. It doesn't happen all the time, but only on certain documents. It appears to be related to the interrelation of spanning headers, footnotes, and balanced columns. A combination of spanning headers with footnotes will do it, and balanced columns can make it worse. .
It doesn't happen all the time, but seems at its worst with a longer document (20+ pages) and lots of footnotes. I think it's a function of these factors, and is triggered by situations in the text which leave the app confused about where to place a footnote when the text reflows. It most commonly occurs when I'm editing text.
I've made a workaround in which the spanning header styles are set to begin in the next frame (done in the Keep menu). Then, I can flow the text and then set the Keep to start the header Anywhere, bringing the spanning header up where it belongs. If this crashes, then I can turn off the Next Frame setting individually for each header, starting at the beginning of the document. This will usually show me which header is causing the problem, and then I can twiddle with frames. If there are edits to be done, I set all the headers to Next Frame, edit, and then undo the Next Frame setting. Byzantine, but it gets the job done.
Yes, it's a bug, and one that Adobe has not been able to fix for a couple years.