Skip to main content
J
jianaaa
Participant
August 10, 2026
Question

Preflight crashes with "std::system_error" exception and garbled error text

  • August 10, 2026
  • 2 replies
  • 194 views

Summary:
The Preflight tool crashes when running a preflight profile on a specific PDF. The error dialog shows a standard library exception with garbled/mojibake text instead of a readable error message.

Steps to Reproduce:
1. Open the PDF in Acrobat Pro.
2. Go to Tools > Print Production > Preflight.
3. Select a preflight profile and click "Analyze" (or "Analyze and Fix").
4. The following error dialog appears immediately:

"Standard library exception of type 'class std::system_error' caught.
Message: [garbled/unreadable characters instead of text]"

Expected behavior:
Preflight should either complete the analysis successfully or show a readable, actionable error message.

Actual behavior:
Preflight crashes with an undecoded/garbled exception message, and the analysis cannot complete.

Additional notes:
- The issue appears to affect the error message encoding itself, suggesting a possible locale/encoding mismatch (system is set to Korean).
- This happens consistently with [this specific PDF / multiple PDFs - 해당사항 선택].
- I have not been able to identify a specific preflight profile or PDF element that triggers this reliably.

Attachments:
- Screenshot of the error dialog (attached)
- Crash logs collected via the Adobe Log Collector Tool (attached, Log ID: [로그 수집 후 ID 입력])

Thank you for looking into this.

      2 replies

      P
      Community Manager
      Pom_9MingCommunity Manager
      Community Manager
      August 21, 2026

      This issue can occur if the file name contains Korean characters. Could you please try renaming the file to English and see if it works?

      M
      masahiroE63
      Participant
      August 17, 2026

      I may have encountered the same or a very similar issue in my environment.

      When I ran Preflight on a PDF with Japanese characters in the filename, I got a similar error. After renaming the file so that the entire file path contained only ASCII characters, Preflight completed successfully.

      For example:
      印刷用データ.pdf → print_data.pdf
      인쇄용_데이터.pdf → print_data.pdf

      I’m not sure whether the underlying cause is the same, but if your filename or file path contains non-ASCII characters, trying an ASCII-only filename/path may be a possible workaround.


      Sharing this in case it helps narrow down the issue.

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