It's hard to tell. Your really did a lot to solve the problem. Just one more question. Does InDesign crash while you are working with «old» files?
If yes, try to export the files to IDML, then double-click the IDML-file. Then InDesign will build a new InDesign file from scratch.
Perhaps it is best to contact Adobe InDesign Support. Let me know if you experience problems contacting support (that shouldn't be the case). I will help you with this.
Daniel (from Switzerland)
Thanks for your reply. This is definitely something I've considered as a potential problem, but unfortunately crashes occur when working with new files as well as old.
Is a member of the InDesign Support available for contact on this forum? The Adobe support page here: What are my contact options? gave me the impression I was unable to contact Adobe directly for any troubleshooting issues not relating to CC.
Do you have any non-Adobe plugins installed? Any Chrome or Firefox plugins? Wacom Tablet?
No non-Adobe plugins installed, nor Chrome/Firefox/Safari Extensions.
A Genius M610X Digitising Tablet was in use several months ago, however this was introduced weeks after the crashes began and regardless has not been installed or used since OSX was reinstalled.
Did you remove its drivers?
This really seems like a software conflict. have you tried starting the Mac with the Shift key down to disable startups? Using a different user account? Disabling Papercut?
I'll try working in safe mode today. I apologise; when I say OSX was reinstalled I mean the OS partition was reformatted and then OSX installed on top. There is therefore no trace of the Digitiser on the computer at the current time. I tried a differing user quite early on, however this had no effect. After the format only documents were transferred; no Library contents etc.
We disabled and removed PaperCut from the computer for a few weeks, but still experienced crashes. It ended up being too awkward to continue.
I'll let you know how safe mode goes.
Safe mode didn't work out too well. Unfortunately several job-critical user fonts became unavailable in safe mode and the computer had to be returned to normal after a few hours as it became essentially useless. No crashes occurred in this time, but that really doesn't prove anything.
It would appear there are considerations to move to CC; do you believe an upgrade could fix the problem at hand?
Well it does reinforce the probability of a conflict with some background program. Chrome plugins are known to cause trouble, among other things.
I will remove Chrome completely. Crashes can be days apart at times, so results may not be instant.
Installed programs post-reformat are now down to Konica Minolta drivers, Papercut, Office 2011 and Firefox.
Regarding CC as previously mentioned; given the little we know about the problem, what do you believe are the chances of its migration to the CC suite if we were to upgrade (with Adobe cleaner)?
I'd say the odds are good that won't help if it turns out to be an external program.
Chrome's uninstallation has had no impact on the crashes. In additional news, Bridge has begun to crash quite often as well, see the URL below for a Pastebin of its crash report.
This may be a completely different issue, it is however repeatable and hence I will describe it in the event it helps trace the problem with Indesign: The crashes occur directly after opening it for the first time after a shutdown/restart. The program 'bounces' in the dock for an unlimited amount of time; the application having stopped responding in the background and therefore must be force closed. The linked crash report then displays and subsequent Bridge starts are successful. At least until the next start-up.
I've installed Parallels on the device for printing and am planning on removing the Konica Minolta drivers and Papercut again. Essentially after that I'll be at a complete loss as to the problem at hand. Similar devices on campus are using CS6 or even CS5 with very similar application set-ups without any problems whatsoever.
Have you try using Disk Utility to repair disk permissions.
Thanks for the assistance in debugging this problem. Unfortunately the errors continued despite the ideas on this post.
We have since purchased and installed CC after another clean uninstallation of CS6, and the errors disappeared instantly, even while working with the same files and projects.
This leads me to suggest the issues I was fighting were some kind of incompatibility between the 27" iMac (prehaps a framework in use) and CS6. Especially since we have ProBooks running the exact same software and OS versions which have never exhibited errors, despite use by the same user.
I've marked this thread as answered.