-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Error code: Crashpad_NotConnectedToHandler #4912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, it happens when CEF was not shutdown properly (application terminated) and when PersistSessionCookies set to True. It seems that Chromium tries to restore window but it doesn't work with CEF. And "--hide-crash-restore-bubble" which is now default doesn't help. |
my app doesn't stores sessions. this is 100% not a window restore issue. |
Try enabling crashpad see https://github.com/cefsharp/CefSharp/wiki/Trouble-Shooting#crash-reporting If the problem persists then you'll need to raise an issue at https://github.com/chromiumembedded/cef/issues Please post a link back here for reference if you do. There have been major upstream changes see chromiumembedded/cef#3685 for background |
@amaitland thanks! after I add crash_reporter.cfg the error changed to |
Check the log file for a more detailed error. If there isn't one then analyse the crash dump generated by crashpad, get a stack trace Search the CEF issue tracker for existing issues. https://github.com/chromiumembedded/cef/issues If you cannot find an issue that matches then create a new one. |
Is there an existing issue for this?
CefSharp Version
127.3.50.0
Operating System
Windows 11
Architecture
x64
.Net Version
4.8.2
Implementation
WinForms
Reproduction Steps
randomly time by time
Expected behavior
loaded content
Actual behavior
Regression?
happens after upgrade 124->127 and CefSharpSettings.RuntimeStyle = CefRuntimeStyle.Chrome;
never seen before on earlier versions.
Known Workarounds
No response
Does this problem also occur in the CEF Sample Application
not tested
Other information
No response
The text was updated successfully, but these errors were encountered: