Participant

Open for Voting

Photoshop 27.9.1 crashes during automated text fitting – 0xc0000005

3 replies
23 views
Translate

Adobe Photoshop 27.9.1 — Repeated Native Text Engine Crash During Automated Text Fitting

Environment

- Application: Adobe Photoshop 27.9.1

- Operating system: Windows 10 Pro (Build 19045)

- Integration: Photoshop scripting / UXP automation

- Crash date: October 26, 2026, at 23:40:09 (UTC+03:00)

Problem

I am developing an automated text-fitting integration for Adobe Photoshop.

During controlled operations involving paragraph text measurement, resizing, and rich text formatting, Photoshop has experienced native crashes.

The Adobe Crash Reporter recorded:

- Exception: EXCEPTION_ACCESS_VIOLATION

- Exception code: 0xc0000005

- Crashing function: OptycaImpl::NormalizeInput

- Related stack frames:

- InputOutputHBImpl::getInputClusters

- WRFontContextComponent::Info

- OptycaImpl::SetClientEncoding

Some controlled text resizing operations succeed, including preserving text styles and undoing changes. However, failures occur in other text-fitting scenarios.

A separate rich-text growth preflight also returned Photoshop error 1205 with an uncertain operation outcome. I have not confirmed whether that error and the native crash share the same root cause.

Expected behavior

Photoshop should safely measure and resize paragraph text while preserving fonts, colors, text ranges, Unicode content, and document geometry. Invalid or unsupported operations should return a clear error rather than terminate Photoshop.

Actual behavior

Photoshop terminates unexpectedly during certain automated text operations.

Questions for Adobe Engineering

1. Is this crash signature a known issue in Photoshop 27.9.1?

2. Are there known limitations involving automated paragraph text resizing, rich-text descriptors, or Unicode text shaping?

3. Is there a supported API workflow or workaround that avoids this native crash?

4. Can this report be escalated to the Photoshop engineering team for investigation?

I can provide the crash report, diagnostic logs, and a controlled reproduction case through an appropriate secure channel.

Thank you.

jane-e

Community Expert

@Imaginative_Gleam1375

This forum is for plug-in developers. Please repost to the Photoshop forum where this issue has been discussed previously.

https://community.adobe.com/p/photoshop

Jane

Translate

P

Peaceful_fun1095

Participant

The getInputClusters frame caught my attention. I wonder if the crash depends on the text itself, rather than just the resizing operation.

One thing worth trying is the same fitting operation with plain ASCII text, then with combining characters or emoji sequences. If ASCII works consistently but certain Unicode sequences trigger the crash, that might help narrow it down to the shaping or cluster-handling path.

I'd also check whether any style range boundaries fall inside a grapheme cluster after the text is modified. Character offsets and visible character boundaries don't always line up, especially with combining marks and ZWJ sequences.

None of that proves it's a Unicode bug, of course. But a minimal example that changes only the text content while keeping the layout and fitting operation identical could be quite useful for Adobe's engineering team.

Translate

I

Imaginative_Gleam1375Author

Participant

Thank you for the detailed suggestions. Your observation about "getInputClusters" is particularly helpful.

The crash occurs in Photoshop 27.9.1 during automated paragraph text fitting, and the crash report shows a native access violation ("0xc0000005") in the text-processing stack.

I agree that comparing text content while keeping the layout and fitting operation unchanged could help isolate the trigger. I’m especially interested in determining whether the issue depends on Arabic/RTL or other Unicode sequences, mixed-style text, or the text modification operation itself.

Because previous live tests have caused Photoshop to crash, I’m preserving the crash evidence and avoiding further crash-prone tests until I can establish a safe, minimal reproduction case.

Based on your experience, would you recommend starting with a plain ASCII-only text case and then changing only the text content, or is there a more specific test that would help distinguish a text-shaping issue from a paragraph-fitting issue?

Thanks again for taking the time to help.

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.