-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Description
Is there an existing issue for this?
- I have searched both open/closed issues, no issue already exists.
CefSharp Version
129.0.11.0
Operating System
Windows 11
Architecture
x64
.Net Version
.net 4.8
Implementation
WPF
Reproduction Steps
Create a new 64-bit CefSharp.WinForms (or WPF) application targeting .NET Framework 4.8.
Initialize CefSharp with the following CefSettings:
AddOrAppend(settings, "disable-features",
"AutofillServerCommunication,AutofillAllowNonHttpActivation,PasswordManagerOnboardingAndroid,PasswordManagerRedesign");
AddOrAppend(settings, "disable-save-password-bubble", "1");
AddOrAppend(settings, "disable-single-click-autofill", "1");
AddOrAppend(settings, "disable-password-generation", "1");
AddOrAppend(settings, "disable-plugins-discovery", "1");
AddOrAppend(settings, "disable-java", "1");
AddOrAppend(settings, "disable-popup-blocking", "1");
AddOrAppend(settings, "ignore-autocomplete-off-autofill", "1");
Open a browser window and navigate to any page that contains a <textarea> (for example, a KendoTextArea bound to a data model).
Focus on the textarea or interact with it (typing, pasting, or programmatically setting text).
The application crashes immediately or shortly after, with an AccessViolation in libcef.dll at sqlite3_dbdata_init.
Expected behavior
CefSharp application should initialize successfully with autofill and password manager features disabled.
<textarea> or KendoTextArea components should be interactable (typing, pasting, or binding to data) without crashing. No AccessViolation exceptions should occur in libcef.dll during normal usage of text input fields. ### Actual behavior Application crashes immediately or intermittently when a <textarea> or KendoTextArea is rendered. Crash occurs in libcef.dll with an access violation (0xc0000005) at sqlite3_dbdata_init. The crash happens even when autofill, password manager, and related features are disabled via CefSettings.CefCommandLineArgs. The stack trace indicates a null pointer dereference in Chromium’s SQLite initialization. ### Regression? This issue did not occur in previous versions of CefSharp / Chromium (e.g., prior to version 129.x). Likely introduced in recent CEF or CefSharp updates where SQLite / Autofill initialization changed. ### Known Workarounds Disable all autofill/password manager features via command-line args (e.g., disable-features=AutofillServerCommunication,AutofillAllowNonHttpActivation,PasswordManagerOnboardingAndroid,PasswordManagerRedesign) — partially mitigates crash, but may not fully prevent it. Test using the official 64-bit CefSharp release instead of a custom build. Avoid using kendoTextArea or <textarea> in CEF UI threads until the crash is fixed. ### Does this problem also occur in the CEF Sample Application Yes using WPF/OffScreen command line args ### Other information CEFSharp version: 129.0.11.0 Platform: Windows 10 x64, .NET Framework 4.8 Browser type: Off-screen / WindowlessRenderingEnabled = true Crash module: libcef.dll, crash in sqlite3_dbdata_init (access violation) Reproduction component: Angular kendoTextArea bound to model Command-line args used: disable-features=AutofillServerCommunication,AutofillAllowNonHttpActivation,PasswordManagerOnboardingAndroid,PasswordManagerRedesign disable-save-password-bubble=1 disable-single-click-autofill=1 disable-password-generation=1 disable-plugins-discovery=1 disable-java=1 disable-popup-blocking=1 ignore-autocomplete-off-autofill=1 Steps already tried: Disable all autofill/password manager features Tested with both default and custom CEFSharp 64-bit builds Tried removing kendoTextArea binding (plain textarea) Dump file: Attached dumps1.dmp Observed behavior: Application crashes immediately when textarea/kendoTextArea is rendered, libcef.dll access violation at sqlite3_dbdata_init. [0x0] libcef!sqlite3_dbdata_init+0x8b4f4a 0xc0192bd5c0 0x7fff607d4480 [0x1] libcef!sqlite3_dbdata_init+0x18b5ee0 0xc0192bd620 0x7fff5f7d278e [0x2] libcef!sqlite3_dbdata_init+0x8b41ee 0xc0192bd650 0x7fff5f8320b8 [0x3] libcef!sqlite3_dbdata_init+0x913b18 0xc0192bd6a0 0x7fff608bd6d4 [0x4] libcef!sqlite3_dbdata_init+0x199f134 0xc0192bd700 0x7fff5f83acaa [0x5] libcef!sqlite3_dbdata_init+0x91c70a 0xc0192bd7b0 0x7fff5f841471 [0x6] libcef!sqlite3_dbdata_init+0x922ed1 0xc0192bdbe0 0x7fff5f840fe7 [0x7] libcef!sqlite3_dbdata_init+0x922a47 0xc0192bdf60 0x7fff5e7e5194 [0x8] libcef!CrashForExceptionInNonABICompliantCodeRange+0x2949ee4 0xc0192be0a0 0x7fff5f4f0cc7 [0x9] libcef!sqlite3_dbdata_init+0x5d2727 0xc0192be100 0x7fff5e9275c1 [0xa] libcef!CrashForExceptionInNonABICompliantCodeRange+0x2a8c311 0xc0192be450 0x7fff5820235f [0xb] libcef!cef_time_from_basetime+0xe62eff 0xc0192bea10 0x7fff5a611f63 [0xc] libcef!GetHandleVerifier+0x1c68b53 0xc0192bed70 0x7fff5a70e207 [0xd] libcef!GetHandleVerifier+0x1d64df7 0xc0192bee40 0x7fff5a6133d7 [0xe] libcef!GetHandleVerifier+0x1c69fc7 0xc0192beed0 0x7fff5a65b013 [0xf] libcef!GetHandleVerifier+0x1cb1c03 0xc0192bf060 0x7fff5a5d21fd [0x10] libcef!GetHandleVerifier+0x1c28ded 0xc0192bf160 0x7fff5a6ff5a7 [0x11] libcef!GetHandleVerifier+0x1d56197 0xc0192bf200 0x7fff5a5c5514 [0x12] libcef!GetHandleVerifier+0x1c1c104 0xc0192bf440 0x7fff583db643 [0x13] libcef!cef_time_from_basetime+0x103c1e3 0xc0192bf4f0 0x7fff589b84d6 [0x14] libcef!GetHandleVerifier+0xf0c6 0xc0192bf560 0x7fff58404e1f [0x15] libcef!cef_time_from_basetime+0x10659bf 0xc0192bf5e0 0x7fff572fb14b [0x16] libcef!cef_zip_reader_create+0x560cb 0xc0192bf6b0 0x7fff5735bc1f [0x17] libcef!cef_zip_reader_create+0xb6b9f 0xc0192bf760 0x7fff583d566f [0x18] libcef!cef_time_from_basetime+0x103620f 0xc0192bf7c0 0x7ff8b10d259d [0x19] kernel32!BaseThreadInitThunk+0x1d 0xc0192bf850 0x7ff8b292af78 [0x1a] ntdll!RtlUserThreadStart+0x28 0xc0192bf880 0x0