IronPDF: How to Fix Orphaned CEF Processes for App Crash Cleanup on macOS ARM

Overview

On macOS ARM, IronPDF 2026.4.1 can leave its Chromium Embedded Framework (CEF) subprocess running after your application crashes, so the process appears to hang and never exits. Updating the IronPdf packages to 2026.5.2 resolves this.

Version Metadata

Minimum Version: 2026.4.1
Superseded-in Version: 2026.5.2

Steps

Update the IronPdf NuGet packages to 2026.5.2 or later. Using the .NET CLI:
```
dotnet add package IronPdf.MacOs.ARM --version 2026.5.2
```
Or in the Visual Studio Package Manager Console:
```
Update-Package IronPdf.MacOs.ARM
```
Rebuild and run your application again.
After the application exits or crashes, confirm no IronPDF or Chrome processes remain. On macOS:
```
ps aux | grep -iE "ironpdf|ironcef|chrome"
```

You should see no leftover IronPDF, IronCefSubprocess, or Chrome gpu-process entries.

Notes and Limitations

Affected setup: IronPdf.MacOs.ARM 2026.4.1 (native interop 2026.4.0.1), macOS ARM64, .NET 10. The hang after a crash was observed on this version and reported resolved after updating to 2026.5.2.
On the affected version, these did not resolve the issue:
- Setting Installation.TempFolderPath.
- Calling IronPdf.IronPdfEngine.Shutdown(). The IronPdfEngine type is not part of the IronPdf.MacOs.ARM package, so this call does not compile against it.
The log warning IronSoftwareDeploymentConfigurationMissingException about QPdf*.deployment.json is non-blocking. qpdf still deploys and loads, and this warning is unrelated to the hanging process.
If you still see orphaned processes on 2026.5.2 or later, enable file logging with Logger.LoggingMode = Logger.LoggingModes.File and share the log with support.