Customer HUB
Skip to content
English
Go to ironsoftware.com
  • There are no suggestions because the search field is empty.

IronPdf.UpdatedChrome: Layout Changes, Renderer Crash, WebSQL or 32-bit Build Errors

Overview

In 2026.11.1, IronPdf.UpdatedChrome and the -updatedchrome IronPdfEngine Docker images moved from Chromium 131 (127 on macOS) to Chromium 146. The newer browser engine lays out pages differently, crashes sooner on very deeply nested HTML and has no WebSQL, and the UpdatedChrome packages no longer support 32-bit processes. Re-baseline your expected output, fix the affected HTML or build, or use the default Chromium 109 engine for content that depends on old behaviour.

IronPdf.Exceptions.IronPdfNativeException: Error while generating PDF from HTML: 'Error while rendering pdf from html for job group 4: 'The browser render process crashed during the PDF print operation (this is also how an out-of-memory condition is reported on some platforms).''. error : Up-to-date Chrome packages for IronPdf no longer support 32-bit processes.

Environment

  • OS: Windows x64, Linux x64/ARM64, macOS x64/ARM64
  • Hosting: In-process (IronPdf.UpdatedChrome packages) or IronPdfEngine Docker :<version>-updatedchrome / :updatedchrome
  • Language/Runtime: .NET; Java, Python and Node.js through the -updatedchrome Docker engine

Version Metadata

  • Version found: 2026.11.1
  • Version resolved: N/A

Cause

Chromium 146 changes font rendering, line breaking, pagination and CSS support; for example, an A4 page is 595.92pt wide on Chromium 146 and 131, but 594.96pt on Chromium 109. Its render process also crashes on deeply nested HTML sooner, Chromium removed WebSQL in Chromium 119, and the UpdatedChrome packages for Windows contain 64-bit files only. The default IronPdf package and the default Docker tags (:<version>, :latest) still use Chromium 109 and aren't affected.

Solution

  1. Recommended: Confirm which engine produced the PDF. In-process (.NET), check whether the project references IronPdf.UpdatedChrome (or .Linux / .MacOs) or the default IronPdf package. In Docker, check the first log line, which exists from 2026.11.1: 
    docker logs <container> 2>&1 | head -1 
    IronPdfEngine Chromium engine: updatedchrome (Chromium 146.0.7680.179, CEF 146.0.12+g6214c8e)

Fonts, spacing or page breaks differ

  1. Run your visual or golden-file tests and accept the new output as the baseline. Output after the engine change is not pixel-identical.
  2. If the output must match a Chromium 109 system exactly, use the default IronPdf package or the default Docker tag :<version>.

"The browser render process crashed" on a render that used to work

  1. Check the HTML for very deep nesting and flatten it, for example by replacing nested wrappers with sibling elements. On Windows, Chromium 146 crashes at about 480 nested elements (Chromium 109 handles 600). On Linux and Docker, nesting written in the HTML renders normally; only trees built by JavaScript crash, at about 2,500 levels (about 4,000 on Chromium 109).
  2. If you can't change the template, render it with the default engine: the IronPdf package or the default Docker tag.

Page script errors around openDatabase

  1. On Chromium 146, openDatabase is undefined and calls throw ReferenceError. On Chromium 109 it worked, and on Chromium 131 it existed but threw SecurityError, so code that checks if (window.openDatabase) can now take a different path. Replace WebSQL with IndexedDB, Web Storage or server-side data, which work on every engine.
  2. Until then, render those pages with the default engine.

Build error "no longer support 32-bit processes" (Windows)

  1. Build the app as 64-bit. For IIS, also set Enable 32-Bit Applications to False on the application pool. 
    <PlatformTarget>x64</PlatformTarget>
  2. Check AnyCPU projects with Prefer 32-bit turned on, especially .NET Framework projects. They build without the error, but render on Chromium 109 instead of 146 without any warning. Check that the process is 64-bit, then clear Prefer 32-bit: 
    Console.WriteLine(Environment.Is64BitProcess); 
    <Prefer32Bit>false</Prefer32Bit>
  3. If the app must stay 32-bit (for example because of a 32-bit COM dependency), use the default IronPdf package, which supports 32-bit on Chromium 109.

Short-term rollback

  1. Pin IronPdf.UpdatedChrome 2026.10.3 (Chromium 131) while you re-baseline. Use this briefly only, because that engine gets no further updates.

References

Copyright © 2026, Iron Software