John, here is that paste. I am also getting several times a day an issue with IDD CS5.5 where I try and paste text in or place an image and get spinning rainbow of death and must force quite to restart IDD. When this happens, CPU drain skyrockets. Here is the pastebin link:
Further to this issue, I have had FIVE Indesign crashes just this morning. One might have been related to a glitched EPS file. But also using eyedropper to dip a color to make a swatch...produces spinning rainbow, cannot quit or do anything in the app, must force quit, losing any unsaved work, re-open with recovery. I am convinced I have a fatal issue with this install, anyone, please...help? Delete entire indesign with app cleaner, start fresh with re-install?
When this happens, CPU drain skyrockets. Here is the pastebin link:
Hmm. Well, it's doing one thing and one thing only, but for annoying technical reasons we can't tell what that thing is, only that it is "0x13730c30."
Can you please, next time this happens, in Activity Monitor, choose View > Send Signal: Abort (SIGABRT)? That will force a crash. Then upload the crash report to http://pastebin.com. Usually I ask for both of those but for some reasons I didn't think it was necessary in your case -- I was wrong!
Further to this issue, I have had FIVE Indesign crashes just this morning.
Seeing those crash reports might be helpful, too. Do you actually mean crashes, where the program quits, or are they just hangs,
requiring you to Force Quit it yourself?
Delete entire indesign with app cleaner, start fresh with re-install?
App cleaner? You should remove InDesign with it's own uninstaller, before using any other cleaning tools.
But reinstallation is a fine thing to try, if you don't want to go down the diagnostic path. Even odds that it won't help, but it doesn't hurt.
OK, not sure I have seen an uninstaller, but I am sure it is there. If it hangs again (yes it is hanging with spinny rainbow most of the time but also a couple of full-on crashes) if it continues I will post the crach report.
The >100% CPU usage is due to having a multicore system that can spread the work of applications that aren't multicore aware. I've had some painful layouts that cause InDesign to take 380% of my quad core xeon on my mac, bringing it to a similar halt in responsiveness.
In my experience it was due to newer versions of InDesign handling EPS files poorly. Using TIF files cured what ailed it in the case of one problem layout. Using an uncompressed file format at typical rather than high quality settings could work for you.
Round tripping your files through an indd > inx > indd may also help. Ensuring that you have a light load of fonts and none of them are duplicates can also be a huge help.
Oh, were we concerned about the 100.7%? It's either due to multicore systems or round-off error, but certainly ID shouldn't use that much under normal circumstances, so clearly something is wrong.
John and Macinbytes: OK, it hung while outputting the package of the project in question, so I aborted in Activity Monitor and have posted the crach report here: http://pastebin.com/XjuJY8Z8
Outputting a package, yeah, well, I was going to say:
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ...esign.Package and Preflight 0x1375196f 0x136ae000 + 670063
1 ...esign.Package and Preflight 0x13751c30 0x136ae000 + 670768
2 ...esign.Package and Preflight 0x13751c30 0x136ae000 + 670768
3 ...esign.Package and Preflight 0x13751b90 0x136ae000 + 670608
4 ...esign.Package and Preflight 0x1374d977 0x136ae000 + 653687
5 ...esign.Package and Preflight 0x137553f9 0x136ae000 + 685049
6 ...esign.Package and Preflight 0x137aa91d GetPlugIn + 271597
7 ...esign.Package and Preflight 0x137ae035 GetPlugIn + 285701
8 ...adobe.InDesign.AppFramework 0x1242fe37 GetPlugIn + 45687
9 ...adobe.InDesign.AppFramework 0x124303f9 GetPlugIn + 47161
10 ...adobe.InDesign.AppFramework 0x1242f70f GetPlugIn + 43855
11 PublicLib.dylib 0x01336c53 CSubject::ModelChange(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*, LazyNotificationData*) + 131
12 com.adobe.InDesign.Links 0x188ac9f7 GetPlugIn + 160967
13 ...adobe.InDesign.AppFramework 0x12513f7a GetPlugIn + 979898
14 ...adobe.InDesign.AppFramework 0x125141b3 GetPlugIn + 980467
15 ...adobe.InDesign.AppFramework 0x124137c2 0x12400000 + 79810
16 ...adobe.InDesign.AppFramework 0x1241a621 0x12400000 + 108065
17 PublicLib.dylib 0x0124c32b CmdUtils::ProcessCommand(ICommand*) + 59
18 com.adobe.InDesign.Links 0x188a2d91 GetPlugIn + 120929
19 ...esign.Package and Preflight 0x136c650a 0x136ae000 + 99594
20 ...esign.Package and Preflight 0x136c7179 0x136ae000 + 102777
21 ...gn.Package and Preflight UI 0x1b976605 GetPlugIn + 543125
22 ...gn.Package and Preflight UI 0x1b976816 GetPlugIn + 543654
23 ...gn.Package and Preflight UI 0x1b97696a GetPlugIn + 543994
24 ...gn.Package and Preflight UI 0x1b972f3b GetPlugIn + 529099
25 com.adobe.InDesign.Actions 0x1a73cde3 GetPlugIn + 11699
26 com.adobe.InDesign.Actions 0x1a742adb GetPlugIn + 35499
27 ...adobe.InDesign.AppFramework 0x12401cf3 0x12400000 + 7411
So, this crash was either due to Packaging or Preflight. Astoundingly, based on previous experience, I think this one actually is because of Live Preflight. Try turning it off.
I thought your crashes were actually more random, not based on a particular action. Does it usually succeed in packaging this document, or is this a reproducible crash?
I don't think Macinbytes' experience is very generalizable, though. We'll see...
John I really REALLY appreciate your help. But I am thinking this issue was caused by a glitch inside this particular document, because I just had to open 14 new IDD files emailed to me from a client and all - while really simple docs - opened and I could live preflight them OK. So I am going to move on and monitor this issue. I will post back here if anything changes. Thanks again.
Oh yes, it's almost certainly a combination of Preflight and the document itself.
When we see this, it's approximately every 3 man-hours or so. Infrequent enough to be quite tough to track down, but very annoying.