Orphaned CEF Subprocess on macOS ARM After a Crash

Curtis Chau

Updated: August 21, 2026

Download IronPDF

• NuGet Download
• DLL Download
• Windows Installer

• ---

• Start Free Trial

Copy for LLMs

• Copy for LLMs

  Copy page as Markdown for LLMs
  # Orphaned CEF Subprocess on macOS ARM After a Crash 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. The affected setup is `IronPdf.MacOs.ARM` `2026.4.1` (native interop `2026.4.0.1`) on macOS ARM64 with .NET 10. The hang after a crash was observed on this version and reported fixed after moving to `2026.5.2`. ## Solution ### 1. Update the NuGet Packages Move the `IronPdf` packages to `2026.5.2` or later. With the .NET CLI: ```bash dotnet add package IronPdf.MacOs.ARM --version 2026.5.2 ``` Or from the Visual Studio Package Manager Console: ```bash Update-Package IronPdf.MacOs.ARM ``` ### 2. Rebuild and Run Rebuild your application and run it again. ### 3. Confirm No Processes Remain After the application exits or crashes, check that no IronPDF or Chrome processes are left behind. On macOS: ```bash ps aux | grep -iE "ironpdf|ironcef|chrome" ``` You should see no leftover IronPDF, `IronCefSubprocess`, or Chrome `gpu-process` entries. ## Notes and Limitations On the affected version, the following did **not** resolve the issue: - **Setting `Installation.TempFolderPath`:** no effect on the orphaned process. - **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 the warning is unrelated to the hanging process. If orphaned processes still appear on `2026.5.2` or later, turn on file logging and send the log to support: ```csharp Logger.LoggingMode = Logger.LoggingModes.File; ```

• ---

• Open in ChatGPT

  Ask ChatGPT about this page
• Open in Gemini

  Ask Gemini about this page
• Open in Grok

  Ask Grok about this page
• Open in Perplexity

  Ask Perplexity about this page

Share

• Share on Facebook
• Share on X (Twitter)
• Share on LinkedIn

• ---

• Email article

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.

The affected setup is IronPdf.MacOs.ARM 2026.4.1 (native interop 2026.4.0.1) on macOS ARM64 with .NET 10. The hang after a crash was observed on this version and reported fixed after moving to 2026.5.2.

Solution

1. Update the NuGet Packages

Move the IronPdf packages 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 your application and run it again.

3. Confirm No Processes Remain

After the application exits or crashes, check that no IronPDF or Chrome processes are left behind. On macOS:

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.

Notes and Limitations

On the affected version, the following did not resolve the issue:

• Setting Installation.TempFolderPath: no effect on the orphaned process.
• 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 the warning is unrelated to the hanging process.

If orphaned processes still appear on 2026.5.2 or later, turn on file logging and send the log to support:

Logger.LoggingMode = Logger.LoggingModes.File;

Logger.LoggingMode = Logger.LoggingModes.File;

Curtis Chau

Chat with engineering team now

Technical Writer

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

...

Read More