Orphaned CEF Processes on macOS ARM
On macOS ARM, IronPDF 2026.4.1 can leave its Chromium Embedded Framework (CEF) subprocess running after your application crashes. The process appears to hang and never exits.
IronSoftwareDeploymentConfigurationMissingException: QPdf*.deployment.json
The affected setup is IronPdf.MacOs.ARM 2026.4.1 (native interop 2026.4.0.1) on macOS ARM64 with .NET 10. On this build, the CEF subprocess is not torn down when the host application exits abnormally, so IronCefSubprocess and its Chrome gpu-process children stay alive. Updating to 2026.5.2 resolves the behavior.
Solution
1. Update the IronPDF packages
Move IronPdf.MacOs.ARM to 2026.5.2 or later. With the .NET CLI:
dotnet add package IronPdf.MacOs.ARM --version 2026.5.2
dotnet add package IronPdf.MacOs.ARM --version 2026.5.2
Or from the Visual Studio Package Manager Console:
Update-Package IronPdf.MacOs.ARM
Update-Package IronPdf.MacOs.ARM
2. Rebuild and run
Rebuild the project and run your application again to load the updated native interop.
3. Confirm no processes remain
After the application exits or crashes, check for leftover renderer processes:
ps aux | grep -iE "ironpdf|ironcef|chrome"
ps aux | grep -iE "ironpdf|ironcef|chrome"
You should see no leftover IronPDF, IronCefSubprocess, or Chrome gpu-process entries.
Debug Tips
On the affected version, the following did not clear the orphaned process:
- Setting
Installation.TempFolderPath: no effect on the hang. - Calling
IronPdf.IronPdfEngine.Shutdown(): theIronPdfEnginetype is not part of theIronPdf.MacOs.ARMpackage, so this call does not compile against it. - *The
IronSoftwareDeploymentConfigurationMissingExceptionwarning about `QPdf.deployment.json`:** non-blocking. qpdf still deploys and loads, and the warning is unrelated to the hanging process.
Logger.LoggingMode = Logger.LoggingModes.File and share the log with support.

