WritableBitmapInfo - MILERR_WIN32ERROR Exception

[Arunkumar-Murugesan]

Hi Team,

As it is the same scenario, We have faced this issue often.

Issue Details

Application Error - MILERR_WIN32ERROR (Exception from HRESULT: 0x88980003)   at System.Windows.Media.Imaging.WriteableBitmap..ctor(Int32 pixelWidth, Int32 pixelHeight, Double dpiX, Double dpiY, PixelFormat pixelFormat, BitmapPalette palette)
   at CefSharp.Wpf.Rendering.WritableBitmapInfo.CreateBitmap()
   at CefSharp.Wpf.ChromiumWebBrowser.<>c__DisplayClass13.<CefSharp.Internals.IRenderWebBrowser.InvokeRenderAsync>b__12()
   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)

We have already faced this issue in the task https://github.com/cefsharp/CefSharp/issues/1759.

From that, the team said to use the version 51.0.0 instead of using 45.0.0.0. But we just need to know the reason for this issue. In which case this issue will be reproduced? Can't we resolve it by this version itself?

Thanks in advance,

Regards,
Arunkumar Murugesan

[amaitland]

Quick google suggests there is a bug the .Net framework. See http://stackoverflow.com/questions/32297637/system-windows-media-imaging-writeablebitmap-leaking-memory

You'll have to do your own research, submit a PR if you can devise a workable solution.

It's interesting that your the only person to report this problem, so you must be doing something different.

Before posting again please read https://github.com/cefsharp/CefSharp/blob/master/ISSUE_TEMPLATE.md

[amaitland]

https://github.com/Microsoft/dotnet/blob/master/releases/net46/dotnet46-changes.md

Microsoft have fixed a memory leak in writable bitmap, if your not already try .Net 4.6

You can also try removing dirtyrect support as suggested in http://stackoverflow.com/questions/24960650/workaround-for-memory-leak-when-using-writeablebitmap-adddirtyrect

[amaitland]

This issue will be closed in 14 days if there is no further feedback.

[Arunkumar-Murugesan]

@amaitland : Thank you for update. But we haven't used the writable bitmap in our codes.

[amaitland]

Application Error - MILERR_WIN32ERROR (Exception from HRESULT: 0x88980003) at System.Windows.Media.Imaging.WriteableBitmap..ctor(Int32 pixelWidth, Int32 pixelHeight, Double dpiX, Double dpiY, PixelFormat pixelFormat, BitmapPalette palette)

@Arunkumar-Murugesan It's WriteableBitmap that is throwing the exception. It's used to provide High DPI support for the OSR rendering that the WPF version uses.

See https://github.com/cefsharp/CefSharp/wiki/General-Usage#offscreen-rendering-osr for background.

How do you reproduce the problem? Are you using .Net 4.6?

[Arunkumar-Murugesan]

@amaitland : Yes. The exception throwing for WriteableBitmap only. But it is not occurred all the time and it comes in rare case only. We are using,

Product - CI Nuget
Operating System - Win 10
Machine Resolution - 1920 * 1080
Cef Sharp Version - 45.0.0
.Net Framework Version - 4.5
Application - WPF

The problem is, we couldn't get this problem in all the time. that's why we are requesting to you for knowing the reason.

Please let me know the concerns if any.

Regards,
Arunkumar Murugesan

[amaitland]

As I've said looks like a memory leak in . Net. Try upgrading to .Net 4.6

Also version 45 is old and unsupported, no bugs will be fixed in old versions.

[Arunkumar-Murugesan]

@amaitland : Thanks for the update.

[amaitland]

You can also try removing dirtyrect support as suggested in http://stackoverflow.com/questions/24960650/workaround-for-memory-leak-when-using-writeablebitmap-adddirtyrect

If upgrading to .Net 4.6 doesn't solve the problem then based on the advice suggested in the above link I'd suggest anyone facing this problem simply subclass WpfBitmapInfo and override Invalidate, don't invalidate the dirty rect, invalidate the whole bitmap. Implement your own IBitmapFactory and return your custom WpfBitmapInfo implementation.

The other suggestion is to create a WriteableBitmap large enough to cover the whole desktop, I guess this might be possible and only have the downside of initially allocating potentially a large block of memory (which maybe more efficient in some scenarios), for a multi monitor setup you would have to create a Bitmap that covered the suited the largest desktop resolution.

Closing this as wontfix as it appears to be a bug in the .Net framework and not directly related to CefSharp. If someone can provide a reliable method to reproduce this issue then possibly it can be reopened at a later point.

[xmedeko]

@amaitland we've got this exception issue rarely from our users, CefSharp 57, these users have probably .NET 4.5.2 (our app has the minimum requirements .NET 4.5.2).
The CefSharp has the minimum requirements .NET 4.5.2 in the README.md and the problem is clearly in the CefSharp.Wpf.Rendering.WritableBitmapInfo class. If you do not plan to rise the minimum .NET supported version, then I think this issue ought to be reopened.