CefSharp 143 Random Crash in WPF .NET Framework 4.8 x86 Application

[niravshah-bit]

Environment
CefSharp Version: 143.0.90
CEF Version: Chromium 143
Application Type: WPF
Framework: .NET Framework 4.8
Platform: x86 (32-bit)
OS: Windows 10 / Windows 11
Deployment: Office and vessel environments
Browser Usage: Multiple embedded browser instances hosting internal and external web pages
Background

We recently upgraded from CefSharp 120.1.110 to CefSharp 143.0.90.

The primary reason for the upgrade was that CefSharp 143 supports binary deployment and no longer requires separate VC++ Redistributable installation, which simplifies deployment in our vessel environment.

CefSharp 120 was relatively stable in production. After upgrading to CefSharp 143, we started experiencing random application crashes.

Crash Scenarios
Scenario 1 - Application Idle
The application crashes while sitting idle with no user interaction.

Scenario 2 - Concurrent Browser Activity

The application crashes when:
ShipSure is running.
User is simultaneously browsing websites using Chrome or Edge.
System memory usage increases.

The crash is random and not consistently reproducible.

Event Viewer Details
Faulting application name: ShipSure.exe
Version: 2.0.30.630

Faulting module name: WindowsBase.ni.dll
Version: 4.8.9316.0

Exception code: 0xc00000fd

Fault offset: 0x000cfe84

Faulting process id: 0x180c

CefSharp / Chromium Logs Prior To Crash
WARNING:
CefFrameImpl::SendProcessMessage sent to detached frame will be ignored

ERROR:
Registration response error message: DEPRECATED_ENDPOINT

ERROR: DNS config watch failed

WARNING: Discarding multiple pages with target (kb): 0

FATAL: chrome/browser/performance_manager/mechanisms/page_discarder.cc:50

Check failed: outcome.has_value()

The final entry before termination is:

FATAL:chrome/browser/performance_manager/mechanisms/page_discarder.cc:50

Check failed: outcome.has_value()

Questions

1. Is this a known issue in Chromium 143 / CEF 143 / CefSharp 143?
2. Has anyone observed crashes originating from Chromium's Performance Manager or Page Discarder functionality?
3. Can memory pressure in a 32-bit process trigger this failure?
4. Are there recommended command-line switches to disable:

• PerformanceManager
• MemorySaver
• TabFreeze
• TabDiscarding
• PageDiscarder

5. Are there any known regressions compared to CefSharp 120 related to memory management or page lifecycle handling?

Additional Information
We are currently collecting full crash dumps for analysis.
The issue has only been observed after upgrading from CefSharp 120 to CefSharp 143.

Any guidance on whether this is a known Chromium/CefSharp issue or recommended mitigation steps would be greatly appreciated.