UpdatedChrome Engine Upgrade to Chromium 146

Curtis Chau
Curtis Chau
Updated: November 5, 2026

In 2026.11.1, IronPdf.UpdatedChrome and the -updatedchrome IronPdfEngine Docker images moved from Chromium 131 (127 on macOS) to Chromium 146. The newer engine lays pages out differently, crashes sooner on deeply nested HTML, has no WebSQL, and no longer supports 32-bit processes.

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.
Text

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 run Chromium 109 and are not affected.

Solution

Start by confirming 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: read the first log line, present from 2026.11.1:
docker logs <container> 2>&1 | head -1
SHELL
IronPdfEngine Chromium engine: updatedchrome (Chromium 146.0.7680.179, CEF 146.0.12+g6214c8e)
Text

Once you know the engine, apply the fix that matches your symptom.

1. Fonts, Spacing, or Page Breaks Differ

Run your visual or golden-file tests and accept the new result as the baseline. Output after the engine change is not pixel-identical to Chromium 109.

If the output must match a Chromium 109 system exactly, switch to the default IronPdf package or the default Docker tag :<version>.

2. Render Process Crashed on a Render That Used to Work

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, where Chromium 109 handles 600. On Linux and Docker, nesting written directly in the HTML renders normally; only trees built by JavaScript crash, at about 2,500 levels (about 4,000 on Chromium 109).

When the template cannot change, render it with the default engine: the IronPdf package or the default Docker tag.

3. Page Script Errors Around openDatabase

On Chromium 146, openDatabase is undefined and calls throw ReferenceError. It worked on Chromium 109, 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, all of which work on every engine.

Until the page is updated, render it with the default engine.

4. Build Error "no longer support 32-bit processes" (Windows)

Build the app as 64-bit. For IIS, also set Enable 32-Bit Applications to False on the application pool.

<PlatformTarget>x64</PlatformTarget>
XML

Watch out for 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, with no warning. Confirm the process is 64-bit, then clear Prefer 32-bit:

Console.WriteLine(Environment.Is64BitProcess);
C#
<Prefer32Bit>false</Prefer32Bit>
XML

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.

5. Short-Term Rollback

Pin IronPdf.UpdatedChrome 2026.10.3 (Chromium 131) while you re-baseline.

Warning: Use the 2026.10.3 pin briefly only. That engine receives no further updates.

References

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

Ready to Get Started?

NuGet Downloads 22,198,312Version:2026.11just released