System.NullReferenceException: Object reference not set to an instance of an object.

[sukney]

System.NullReferenceException: Object reference not set to an instance of an object.
at CefSharp.Wpf.Rendering.WritableBitmapRenderHandler.<>c__DisplayClass4_0.b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.NullReferenceException: Object reference not set to an instance of an object.
at CefSharp.Wpf.Rendering.WritableBitmapRenderHandler.<>c__DisplayClass4_0.b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
at System.Windows.Media.Imaging.WriteableBitmap..ctor(Int32 pixelWidth, Int32 pixelHeight, Double dpiX, Double dpiY, PixelFormat pixelFormat, BitmapPalette palette)
at CefSharp.Wpf.Rendering.WritableBitmapRenderHandler.<>c__DisplayClass4_0.b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

CefSharp.Wpf Version="86.0.241"

[amaitland]

Converting to discussion as Bug Report wasn't completed. Most often OutOfMemoryException when using CefSharp.Wpf isn't actually a bug in CefSharp at all.

System.OutOfMemoryException: Insufficient memory to continue the execution of the program.

Your process has run out of memory, if you are targeting x86 then make sure your process is LargeAddressAware. See https://github.com/cefsharp/CefSharp/wiki/General-Usage#win32-out-of-memory

Ideally target x64 to access even more memory.

You should also profile your WPF application and fix any memory leaks (there are some very common WPF memory leaks).

• https://blog.jetbrains.com/dotnet/2014/09/04/fighting-common-wpf-memory-leaks-with-dotmemory/
• https://michaelscodingspot.com/ways-to-cause-memory-leaks-in-dotnet/#:~:text=WPF%20Bindings%20can%20actually%20cause,a%20memory%20leak%20(explanation).

There are likely others you can do your own research there.

It might also be worth considering switching to https://www.nuget.org/packages/CefSharp.Wpf.HwndHost/ (think WinForms version hosted in WPF, airspace issues apply).

[amaitland]

See also #2035 (comment)