You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are issues with tests failing, seems like something has changed in CEF/Chromium, Issue #4621 now reproduces all the time. Simply reloading a page appears to create then immediately destroy the CefBrowser in the render process.
That would definitely affect my software then, as I rely on JavaScript and other features that require a browser ID after a reload. I think it is safer for me to hold off on an upgrade until there is a fix.
Thanks for all your hard work in getting to the bottom of this.
Well I'm testing need to dig deeper since the app I'm using is WinForm x64, Net 10 with reference to CefSharp.BrowserSubprocess.Core.dll so the process can be renamed, CefSharp.CefRuntimeStyle.Chrome
And it just crash with libcef error.
I'm checking I can make it work.
settings.CefCommandLineArgs.Add("disable-features", "OptimizationGuideOnDeviceModel");
Removing the above command line arg from the MinimalExample and it stops crashing.
Do you have any command line args set @SorceryAdmin ?
I do have many so I have been trying to get to find which one is the problematic.
Activity
amaitland commentedon Nov 18, 2025
There are issues with tests failing, seems like something has changed in
CEF/Chromium, Issue #4621 now reproduces all the time. Simply reloading a page appears to create then immediately destroy theCefBrowserin the render process.amaitland commentedon Nov 26, 2025
I haven't found an easy way to reproduce the issue with the CEF sample application.
I can disable the two failing tests for now to get the release out. This isn't my ideal though as I don't see a workaround for the issue.
The browser in the render process appears to be created then immediately destroyed when refresh occurs or reloading the same URL.
GrabzIt commentedon Nov 26, 2025
Hi Alex,
Thanks for all the great work you do.
Is the fact that the browser process is being destroyed and recreated causing an issue in the off-screen version? Or will it not be noticeable?
Because my code uses the refresh feature and some webpages will trigger it as well.
Thanks
Dominic
amaitland commentedon Nov 26, 2025
Hi Dominic,
Yes, the offscreen implementation is impacted. If you are evaluating javascript after the reload then it will fail.
I can make a CI build available if you want to test to see if your application is impacted.
Alex
amaitland commentedon Nov 26, 2025
Looks like another CEF user is experiencing a similar problem, related forum thread.
https://www.magpcss.org/ceforum/viewtopic.php?f=6&t=20428
Have added some extra detail, will see if we can get an actionable bug created on the CEF issue tracker.
GrabzIt commentedon Nov 26, 2025
Thanks, Alex.
That would definitely affect my software then, as I rely on JavaScript and other features that require a browser ID after a reload. I think it is safer for me to hold off on an upgrade until there is a fix.
Thanks for all your hard work in getting to the bottom of this.
amaitland commentedon Nov 30, 2025
PR #5197 will restructure to workaround the issue.
@GrabzIt Are you using the old sync javascript binding at all?
GrabzIt commentedon Nov 30, 2025
That's awesome, thanks Alex! No, I don't use the old sync binding.
SorceryAdmin commentedon Dec 1, 2025
I would like to test a CI to see if my App gets impacted and I can let you know what occurs and if find a workaround.
amaitland commentedon Dec 3, 2025
CI Build is now available on https://www.myget.org/feed/Packages/cefsharp
SorceryAdmin commentedon Dec 3, 2025
Well I'm testing need to dig deeper since the app I'm using is WinForm x64, Net 10 with reference to CefSharp.BrowserSubprocess.Core.dll so the process can be renamed, CefSharp.CefRuntimeStyle.Chrome
And it just crash with libcef error.
I'm checking I can make it work.
amaitland commentedon Dec 4, 2025
Tested with the
MinimalExampleand can reproduce the crash with Chrome style, works fine with Alloy. So is very likely aCEFissue.amaitland commentedon Dec 4, 2025
Removing the above command line arg from the
MinimalExampleand it stops crashing.Do you have any command line args set @SorceryAdmin ?
SorceryAdmin commentedon Dec 8, 2025
These are the ones I use.
settings.CefCommandLineArgs.Add("disable-system-fonts", "1");
settings.CefCommandLineArgs.Add("disable-font-subpixel-positioning", "1");
settings.CefCommandLineArgs.Add("disable-lcd-text", "1");
settings.CefCommandLineArgs.Add("disable-font-system-caching", "1");
settings.CefCommandLineArgs.Add("disable-font-antialiasing", "1");
settings.CefCommandLineArgs.Add("disable-font-hint-scaling", "1");
settings.CefCommandLineArgs.Add("force-text-direction", "ltr");
settings.CefCommandLineArgs.Add("force-device-scale-factor", "1");
settings.CefCommandLineArgs.Add("disable-features",
"VizDisplayCompositor,FontAccess,FontAccessAPI,SystemFonts,DirectWrite,GDI,Skia,FontCache,LocalFonts,FontManager,TextInputClient,HarfBuzzShaper,SkiaTextRenderer");
settings.CefCommandLineArgs.Add("force-gpu-mem-available-mb", "2048");
settings.CefCommandLineArgs.Add("max-gum-fps", "60");
settings.CefCommandLineArgs.Add("force-max-texture-size", "16384");
settings.CefCommandLineArgs.Add("memory-pressure-off", "1");
settings.CefCommandLineArgs.Add("enable-win32k-renderer-lock-down", "1");
settings.CefCommandLineArgs.Add("renderer-process-limit", "6");
settings.AcceptLanguageList = "en-US,en";
settings.CefCommandLineArgs.Add("--disable-webrtc");
settings.CefCommandLineArgs.Add("--disable-webrtc-hw-decoding");
settings.CefCommandLineArgs.Add("--disable-webrtc-multiple-routes");
settings.CefCommandLineArgs.Add("--disable-webrtc-smoothness-algorithm");
settings.CefCommandLineArgs.Add("--disable-webrtc-stun-origin");
settings.CefCommandLineArgs.Add("--disable-webrtc-hw-vp8-encoding");
settings.CefCommandLineArgs.Add("--disable-webrtc-hw-vp9-encoding");
settings.CefCommandLineArgs.Add("--disable-webrtc-hw-h264-encoding");
settings.CefCommandLineArgs.Add("--disable-features=WebRtcHideLocalIpsWithMdns");
settings.CefCommandLineArgs.Add("--force-webrtc-ip-handling-policy=disable_non_proxied_udp");
settings.CefCommandLineArgs.Add("-–disable-blink-features", "AutomationControlled");
settings.CefCommandLineArgs.Add("--disable-background-networking");
settings.CefCommandLineArgs.Add("--disable-renderer-backgrounding");
settings.CefCommandLineArgs.Add("--disable-backgrounding-occluded-windows");
settings.CefCommandLineArgs.Add("--disable-ipc-flooding-protection");
settings.CefCommandLineArgs.Add("--no-default-browser-check");
settings.CefCommandLineArgs.Add("--disable-component-extensions-with-background-pages");
settings.CefCommandLineArgs.Add("--disable-features=VizDisplayCompositor");
settings.CefCommandLineArgs.Add("--disable-dev-shm-usage");
settings.CefCommandLineArgs.Add("--enable-proprietary-media-types");
settings.CefCommandLineArgs.Add("--memory-pressure-off");
settings.CefCommandLineArgs.Add("--password-store", "basic");
CefSharp.CefSharpSettings.ShutdownOnExit = true;
CefSharp.CefSharpSettings.RuntimeStyle = CefSharp.CefRuntimeStyle.Chrome;
amaitland commentedon Dec 9, 2025
How does it behave if you remove all the options added to CefCommandLineArgs?
Some of those arguments look outdated and likely no longer exist, few I don't recognize.
amaitland commentedon Dec 10, 2025
Given that 143 is now stable, I'm thinking of skipping 142 and releasing a 143 build (likely on the weekend depending on tests)
GrabzIt commentedon Dec 10, 2025
That sounds like a sensible approach. Thanks for everything!
SorceryAdmin commentedon Dec 11, 2025
It makes sense.
[-]Release Notification - 142.0.x[/-][+]Release Notification - 143.0.x[/+]