Skip to main content
B
Brad Serum
Participant
January 9, 2019
Answered

InDesign crashing (TypeQuest?)

  • January 9, 2019
  • 2 replies
  • 816 views

InDesign crashes after 19 seconds of successful startup. I first discovered this issue around noon PST 1/9/2919.

InDesign was working fine yesterday.

In the intervening time, I made no deliberate changes to my system.

My system:

MacBook Pro (15-inch, Mid 2012)

MacOS High Sierra 10.13.6

The Mac OS Crash report includes:

Crashed Thread:        38  TypeQuest

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

The unsuccessful troubleshooting methods I've tried:

  • Uninstalling InDesign / ReInstallling InDesign (even after removing all (legacy and current) preferences from ~ Library/Preferences/Adobe InDesign
  • Loggin out of / back into my Adobe Creative Cloud account
  • Launching in Safe Mode (Mac)
  • Freeing up additional GB of RAM
  • Disabling all but my base set of fonts

The unsatisfactory workaround I discovered was to disconnect from the Internet before/while running InDesign. For obvious reasons, this is not a tenable long-term solution.

As of this writing, I have been on hold with Adobe's phone support for over an hour.

Please help.

This topic has been closed for replies.
Correct answer prateekgaurav

Hi,

We're very sorry for the interruption. It should be working again.

Regards

Prateek Gaurav

2 replies

prateekgaurav
Adobe Employee
prateekgauravCorrect answer
Adobe Employee
January 10, 2019

Hi,

We're very sorry for the interruption. It should be working again.

Regards

Prateek Gaurav

J
JoeLigo
Inspiring
January 9, 2019

Am observing exactly the same problem (Mac Pro Mid 2010; High Sierra 10.13.6; 16gb ram). App crashes just as described, after 19 seconds. Also, when I try to open an IDML backsave of a layout I created about 2 weeks ago using the same version of InD (14.0.1), the program works long enough to open the file, then crashes as before.

My crash logs consistently make reference to Typequest and the character panel, tho I haven't been able to isolate to any font related problem as yet (here's one of the crashed threads):

Thread 67 Crashed:: TypeQuest

0   com.adobe.InDesign.Character Panel 0x000000011b261362 0x11b243000 + 123746

1   com.adobe.InDesign.Character Panel 0x000000011b25f1ab 0x11b243000 + 115115

2   com.adobe.InDesign.Character Panel 0x000000011b2736c0 0x11b243000 + 198336

3   com.adobe.InDesign.Character Panel 0x000000011b28ee69 0x11b243000 + 310889

4   com.adobe.InDesign.Character Panel 0x000000011b28ed89 0x11b243000 + 310665

5   com.adobe.InDesign.Character Panel 0x000000011b28ebc5 0x11b243000 + 310213

6   libtypekitC4Release.dylib     0x00000001103a76a1 0x110375000 + 206497

7   libtypekitC4Release.dylib     0x00000001103a8189 0x110375000 + 209289

8   libtypekitC4Release.dylib     0x00000001103917b8 0x110375000 + 116664

9   libtypekitC4Release.dylib     0x00000001103c841d 0x110375000 + 341021

10  libtypekitC4Release.dylib     0x00000001103d977f uxtech::thread::Dispatcher::Flush() + 143

11  libtypekitC4Release.dylib     0x00000001103d9aab 0x110375000 + 412331

12  com.apple.Foundation           0x00007fff505010b5 __NSThreadPerformPerform + 334

13  com.apple.CoreFoundation       0x00007fff4e3bfbe1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

14  com.apple.CoreFoundation       0x00007fff4e4774bc __CFRunLoopDoSource0 + 108

15  com.apple.CoreFoundation       0x00007fff4e3a2b90 __CFRunLoopDoSources0 + 208

16  com.apple.CoreFoundation       0x00007fff4e3a200d __CFRunLoopRun + 1293

17  com.apple.CoreFoundation       0x00007fff4e3a1867 CFRunLoopRunSpecific + 487

18  com.adobe.InDesign.Character Panel 0x000000011b270e59 0x11b243000 + 187993

19  com.adobe.InDesign.Character Panel 0x000000011b2856f2 0x11b243000 + 272114

20  libsystem_pthread.dylib       0x00007fff76683661 _pthread_body + 340

21  libsystem_pthread.dylib       0x00007fff7668350d _pthread_start + 377

22  libsystem_pthread.dylib       0x00007fff76682bf9 thread_start + 13

J
JoeLigo
Inspiring
January 10, 2019

Tested this morning and all seems to be working fine. Appreciate the quick response!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices