I didn't set up a new user. WHY do I need to set up a new user? Do you think this will fix my problem?

Creating a new user account is an important diagnostic step.

It lets us make sure that the problem is not related to configuration files or caches assocaited with your current user account, which helps to narrow down a huge category of problems. Also, emperically it often provides a workaround for a large category of problems. You really should try it, it only takes a minute or two to test it.

It is not a "solution" per se, more of a diagnostic tool or a workaround.

Reviewing your crash report, I am not really sure what to say.

How long have you been running 10.7.4? It just came out, and I wonder if it is part of the problem.

The stack of your crashing thread is this:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.adobe.BIB 0x00dd10fe 0xdce000 + 12542

1 com.adobe.BIB 0x00dd1148 0xdce000 + 12616

2 com.adobe.BIB 0x00dd13e3 0xdce000 + 13283

3 com.adobe.BIB 0x00dd1469 0xdce000 + 13417

4 com.adobe.InDesign.PDF 0x1415c820 GetPlugIn + 1222048

5 com.adobe.InDesign.PDF 0x1417a5a6 GetPlugIn + 1344294

6 libsystem_c.dylib 0x9487d944 __cxa_finalize + 243

7 libsystem_c.dylib 0x9487d7f2 exit + 25

8 com.adobe.InDesign 0x00001d5d start + 61

And that means, if this is to be believed, the InDesign startup code (frame 8) is calling the libc exit() function, which then leads to the crash. But why would InDesign decide to exit deliberately? That seems odd.

Is there anything in Console.app?

Then exit() calls __cxa_finalize(), which calls the registered C++ exit handlers that various modules have registered. And the one inside InDesign’s PDF library calls out to AdobeBIB which then crashes. It doesn’t seem too shocking that the exit handler is causing a crash through -- the PDF library probably hasn’t finished initializing and the exit handler is assuming that it has been properly initialized. But it’s really moot -- the question is why the app is trying to exit at all.

And I have no good thoughts on this. Though I saw the same exact problem somewhere else (privately) this morning. Also 10.7.4. Which has me worried.