Locate and interpret Adobe Photoshop crash reports on macOS

Last updated on Oct 4, 2026

Learn how to find crash logs, identify problematic plugins or fonts, and extract diagnostic information from technical reports in Adobe Photoshop.

When Adobe Photoshop crashes on macOS, the system automatically generates a crash report containing technical information about the issue. These reports help identify whether plugins, fonts, or internal issues caused the crash.

After Photoshop unexpectedly closes, always submit the crash report to Adobe through the crash reporter dialog. If you include your email address, Adobe can notify you of solutions for known issues. You can also share crash reports on the Photoshop Community forums or the Bug Report site for community assistance.

Note

A crash (the application closes completely) differs from a freeze (the application stops responding but remains open). For frozen applications, use How to get a Process Sample or Spindump on macOS.

Find and read crash reports

Crash reports are stored in a hidden system folder on macOS that requires specific navigation steps to access.

Open Finder and select Go > Go to Folder from the menu bar.

Type ~/Library/Logs/DiagnosticReports and select Go.

Look for files starting with "Adobe Photoshop" followed by a date and timestamp.

Double-click the most recent crash report to open it in Console, or drag it to TextEdit to view it.

Alternatively, open Console from Applications > Utilities, select Crash Reports in the sidebar, and locate Adobe Photoshop entries.

The crash report opens as a plain text file with technical information organized into sections.

Identifying common crash causes

The following solutions address the most common causes of crashes, organized by frequency.

Understanding the report header

The report header contains essential context about the crash. Look for these key elements:

Process information: Confirms which application crashed and the installation path

Date/Time: Shows when the crash occurred to correlate with your actions

OS Version: Displays your macOS version—ensure your system is up to date

Code Type: Indicates processor architecture (ARM-64 for Apple Silicon, X86-64 for Intel)

Crashed Thread: Identifies which thread failed—this number corresponds to the detailed section below

Within the crashed thread section, the topmost lines show what Photoshop was doing before it crashed.

Plugin-related crashes

Outdated or incompatible third-party plugins can cause crashes, and the crashed thread section reveals which plugin is responsible.

Open the crash report and locate the "Crashed Thread" line near the top—note which thread number crashed.

Scroll down to the section matching that thread number.

Examine the first 5-10 lines of the stack trace for third-party plugin identifiers like com.company.pluginname or non-Adobe framework references.

If you find a plugin reference, move the plugin out of Applications/Adobe Photoshop [version]/Plug-ins to a different location.

Restart Photoshop to test if removing the plugin resolves the crash.

Contact the plugin developer for an updated version compatible with your Photoshop and macOS versions.

Note

Plugin references appear before Adobe's own code in the stack trace.

Font-related crashes

Corrupted font files or font management utilities cause Photoshop's type engine (CoolType) to crash during startup or when accessing text tools.

Open the crash report and search for "CoolType", "font", or "ATS" in the crashed thread section.

Look for lines showing com.adobe.CoolType followed by function names like CTInit.

Check for third-party font management plugins, such as com.extensis.AutoActivationPlugin, in the stack trace.

Disable or update your font management software.

Use macOS Font Book (Applications > Font Book) to validate fonts: select all fonts, then select File > Validate Fonts.

Remove or quarantine any problematic fonts identified during validation.

For comprehensive font troubleshooting, use Troubleshoot fonts in Photoshop.

Internal code crashes

When the crashed thread shows only com.adobe.Photoshop addresses the crash using hexadecimal numbers and no readable function names; the crash occurred in internal Photoshop code that requires analysis by Adobe engineering.

  • Verify your crash report includes the system information section at the top (OS Version, Code Type, Date/Time).
  • Submit the crash report through the Adobe Crash Reporter dialog that appears after crashes.
  • Include your email address in the submission so Adobe can notify you of solutions for known issues.
  • Provide a detailed description of what you were doing when the crash occurred in the crash reporter's comment field.
  • Check for Photoshop updates at Help > Updates that may contain fixes for your crash pattern.
  • Share the crash report on the Photoshop Community forums for additional assistance.
Note

Unresolved crash addresses require Adobe engineers to analyze them using internal debugging symbols.

Additional troubleshooting resources

If crashes persist after analyzing crash reports and implementing the solutions above, use Basic troubleshooting steps for comprehensive guidance on fixing most issues, including preference resets, GPU troubleshooting, and system-level diagnostics.