Does CefSharp supports NET 6.0? Having memory error

[MrGonzy]

Hi, i migrated my project from .NET 4.0 to .NET 6.0. C# Winform. I am using the CEFSharp for this project. With this, i am trying to build the application as a single file using publish. However, after publishing and running my application, i am getting an error below. The issue comes from chrominiumWebBrowser. After making the visible as false, the application can run successfully.

So my question is, does CefSharp supports NET 6 or only NET 4.5++? I hope to get some help with this issue. Thank you.

Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Repeat 2 times:
--------------------------------
   at <Module>._getFiberPtrId()
--------------------------------
   at <Module>.<CrtImplementationDetails>.LanguageSupport._Initialize(<CrtImplementationDetails>.LanguageSupport*)
   at <Module>.<CrtImplementationDetails>.LanguageSupport.Initialize(<CrtImplementationDetails>.LanguageSupport*)
   at <Module>..cctor()
   at CefSharp.Cef.get_IsInitialized()
   at CefSharp.WinForms.ChromiumWebBrowser.InitializeFieldsAndCefIfRequired()
   at CefSharp.WinForms.ChromiumWebBrowser.OnHandleCreated(System.EventArgs)
   at System.Windows.Forms.Control.WmCreate(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr, WM, IntPtr, IntPtr)
   at Interop+User32.CreateWindowExW(WS_EX, Char*, System.String, WS, Int32, Int32, Int32, Int32, IntPtr, IntPtr, IntPtr, System.Object)
   at Interop+User32.CreateWindowExW(WS_EX, Char*, System.String, WS, Int32, Int32, Int32, Int32, IntPtr, IntPtr, IntPtr, System.Object)
   at Interop+User32.CreateWindowExW(WS_EX, System.String, System.String, WS, Int32, Int32, Int32, Int32, IntPtr, IntPtr, IntPtr, System.Object)

[amaitland]

Duplicate of #4444