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
{{ message }}
Repository navigation
v146.0.70 JavaScript CefSharp object not availlable when loading via GET -> POST -> POST (iframe) #5228
Does this problem also occur in the CEF Sample Application
Not Tested
Other information
The following error gets logged:
[61096:32296:0330/115323.606:ERROR:C:\projects\cefsharp\CefSharp.BrowserSubprocess.Core\CefAppUnmanagedWrapper.cpp:404] Failed to identify BrowserWrapper in OnContextCreated BrowserId:1
changed the title [-]v146.0.70 CefSharp object not availlable when loading via GET -> POST -> POST (iframe)[/-][+]v146.0.70 JavaScript CefSharp object not availlable when loading via GET -> POST -> POST (iframe)[/+]on Mar 30, 2026
INDEX PAGE
[87396:13172:0331/110222.002:ERROR:C:\projects\cefsharp\CefSharp.BrowserSubprocess.Core\CefAppUnmanagedWrapper.cpp:68] Added BrowserWrapper in OnBrowserCreated BrowserId: 1 Added: True
[87396:13172:0331/110222.247:ERROR:C:\projects\cefsharp\CefSharp.BrowserSubprocess.Core\CefAppUnmanagedWrapper.cpp:68] Added BrowserWrapper in OnBrowserCreated BrowserId: 1 Added: False
FORM POST SUBMIT
[87396:13172:0331/110222.301:ERROR:C:\projects\cefsharp\CefSharp.BrowserSubprocess.Core\CefAppUnmanagedWrapper.cpp:140] Removed BrowserWrapper in OnBrowserDestroyed BrowserId: 1
FORM POST SUBMIT IFRAME
[87396:13172:0331/110222.594:ERROR:C:\projects\cefsharp\CefSharp.BrowserSubprocess.Core\CefAppUnmanagedWrapper.cpp:420] Failed to identify BrowserWrapper in OnContextCreated BrowserId: 1
The browser is tried to be added twice and then removed once.
When submitting via POST the browser gets destroyed (no other browser gets created though), and then it isn't found anymore.
When submitting via POST the browser gets destroyed (no other browser gets created though), and then it isn't found anymore.
Sounds like a bug in CEF. Any chance you could test with the --disable-request-handling-for-testing command line arg to see if CEF's request interceptor is part of the problem.
FYI: I tested it with 147 (campersau@9f8c038) again and the issue is still there.
I guess it was there previously but we haven't noticed it until #5218
Activity
[-]v146.0.70 CefSharp object not availlable when loading via GET -> POST -> POST (iframe)[/-][+]v146.0.70 JavaScript CefSharp object not availlable when loading via GET -> POST -> POST (iframe)[/+]amaitland commentedon Mar 31, 2026
Possibly because of #5218
amaitland commentedon Mar 31, 2026
Get a 404 when trying to open
campersau commentedon Mar 31, 2026
Yes, it looks like it. Now the
browserWrapperis required, before it wasn't even used to setup the bindings.CefSharp/CefSharp.BrowserSubprocess.Core/CefAppUnmanagedWrapper.cpp
Lines 168 to 170 in 24e7df2
https://github.com/cefsharp/CefSharp/pull/5218/changes#diff-357680293df8761a33d94272a6a9faaa1528bb062412c8d3893de9ba94e030a5R168-R170
https://github.com/cefsharp/CefSharp/pull/5218/changes#diff-357680293df8761a33d94272a6a9faaa1528bb062412c8d3893de9ba94e030a5L154
campersau commentedon Mar 31, 2026
I debugged this a bit with https://ci.appveyor.com/project/campersau/cefsharp/build/artifacts to see when browserwrappers are added / removed. And this is the log:
The browser is tried to be added twice and then removed once.
When submitting via POST the browser gets destroyed (no other browser gets created though), and then it isn't found anymore.
amaitland commentedon Mar 31, 2026
Sounds like a bug in
CEF. Any chance you could test with the--disable-request-handling-for-testingcommand line arg to see if CEF's request interceptor is part of the problem.campersau commentedon Mar 31, 2026
Same output with
amaitland commentedon Mar 31, 2026
Thanks for testing.
campersau commentedon May 5, 2026
FYI: I tested it with 147 (campersau@9f8c038) again and the issue is still there.
I guess it was there previously but we haven't noticed it until #5218
amaitland commentedon May 6, 2026
I think it's relatively recent as there are reports of issues with the WCF channel being disposed starting in 145
#5232
#5233