Frequent Crashes ID CS5 (7.0.4)

Question

I've been getting a freeze — lately it's been on save. Trashed Prefs, ran Cocktail, etc., etc.
MacPro 4-Core, Snow, 8gb RAM
Any decipher this? http://pastebin.com/GQPvENVv
TIA,
Geoff

Answer 1

Well, that's interesting. Let's look at the last 18 stack frames:
17  17 CDocFileHandler::SaveAs(UIDRef const&, IDFile const*, K2::UIFlags, unsigned char, IDType<FileTypeInfoID_tag>) + 265 (in PublicLib.dylib) [0x11835e9]
16  17 CmdUtils::ProcessCommand(ICommand*) + 59 (in PublicLib.dylib) [0x116557b]
15  17 ??? (in AppFramework + 108168) [0x1397a688]
14  17 ??? (in Utilities + 7372) [0x14c90ccc]
13  17 ??? (in Utilities + 6819) [0x14c90aa3]
12  17 Command::DoImmediate(short) + 34 (in PublicLib.dylib) [0x1164422]
11  17 ??? (in Document Actions + 20262) [0x1b442f26]
10  17 ??? (in Document Framework + 38134) [0x158d14f6]
9  17 ??? (in DataBaseLib.dylib + 24575) [0x10cefff]
8  17 DBUtils::GetUIDPersistedInterfaces(IDataBase*, IDType<UID_tag>, IDType<ClassID_tag>, IPMPersist*, std::vector<IDType<ImplementationID_tag>, std::allocator<IDType<ImplementationID_tag> > >&) + 50584 (in DataBaseLib.dylib) [0x10dd798]
7  17 DBUtils::GetUIDPersistedInterfaces(IDataBase*, IDType<UID_tag>, IDType<ClassID_tag>, IPMPersist*, std::vector<IDType<ImplementationID_tag>, std::allocator<IDType<ImplementationID_tag> > >&) + 76020 (in DataBaseLib.dylib) [0x10e3af4]
6  17 ProtectiveShutdown::~ProtectiveShutdown() + 153 (in PublicLib.dylib) [0x11a3f49]
5  17 ??? (in AppFramework + 8093) [0x13961f9d]
4  17 GetPlugIn + 834719 (in AppFramework) [0x13a509cf]
3  17 GetPlugIn + 1018333 (in AppFramework) [0x13a7d70d]
2  17 boost::thread::join() + 189 (in boost_threads) [0x1705c4d]
1  17 pthread_cond_wait$UNIX2003 + 73 (in libSystem.B.dylib) [0x912263f8]
0  17 __semwait_signal + 10 (in libSystem.B.dylib) [0x91224aa2]
So, in the process of saving (frrame 17), we perform some database operations and detect a fault at frame 6, and execute a ProtectiveShutdown.
But the ProtectiveShutdown never completes, it gets stuck doing some thread management task.
Normally in a ProtectiveShutDown, InDesign writes some explanatory data to ~/Library/Caches/Adobe InDesign/Version 7.0/en_us/InDesign Recovery/ProtectiveShutdownLog.
Since it hung in the ProtectiveShutdown, it's hard to know if it managed to write the data or not. So check. It may have useful information on the problem.
I would, however, tend to suspect it is a problem with your document (corruption). Do you see it on more than one document? Have you tried exporting to IDML?