I've realised that the problem with the document mentioned above is related to the fact that the preceding paragraph is split into 2 and contains a 1 column table. If I remove delete this paragraph then I can edit the text with no bother.
The very same problem is described here:
Come on Adobe! Get it sorted!
If you want help, you're going to have to give us more info.
Are you on Mac or Windows? What version?
That thread is for CS5 so it's not likely to be the same thing.
Look at post number 9 in that thread:
"2 years on, and this issue still exists in CS6. Win7/64, 12GB RAM, delayed screen update.
I often - but not always - get it with split columns on a table. Other 'complications' may be column break character following, or an anchored object. I wish I had more time to isolate the issue..."
This thread also seems to be related:
I'm running Windows 7 64 via Bootcamp on a 2011 MacBook
Are you using Span/Split columns?
Are you working with brand new files, or opening legacy files. Was ID a clean install on a clean install of the OS, or some sort of migration?
Yes, I'm using split columns and the crashes seem to be caused by that. If I cut out the split column paragraph then everything works fine.
So what I'm doing at the moment is that if I need to edit any text that might disturb the position in the page of the split paragraph I just cut it out, make the changes to the surrounding text and then paste it back in. A pain but at least I can stop the crashing.
This is a clean install of Indesign on a clean install of win 7.
The first time I experienced a crash like this was with a document that had originally been created in a previous version.
However as the crashes were so frequent (and I didn't know the cause) I created a brand new document.
This brand new document still crashes when using split column paragraphs.
Obviously I could stop using split paragraphs but its a shame as they are very useful.
What can I say? There's a bug, and presumably at some point it's going to get fixed, but nobody here can tell you when.
Where can i report this bug? Or do you think Adobe engineers are aware of it already?