Closed marci4 closed 6 years ago
As part of #2237 the way rendering for the OffScreen
and WPF
projects is done has been rewritten, I've run a slightly modified version of your code (OnPaint
event is now Paint
, there is now a virtual OnPaint
method which is more consistent with the other projects). I changed the counter to 100
and it ran through without exception.
The main difference is that the buffer is stored as a byte[]
now, rather than a Bitmap
, and a Bitmap
is only created upon request, this should improve performance and actually greatly simplifies the code.
Closing this as I'm not unable to reproduce with master
, you can try one of the CI
builds listed at https://github.com/cefsharp/CefSharp#releases-1 to try it out ASAP
.
Will likely be some more changes as part of https://github.com/cefsharp/CefSharp/issues/2237 so subscribe to that issue to be notified of updates.
Sorry to ask, but I'm having the same problem (see closed duplicate above). I'm not sure what you did to fix the problem? Do we have to wait for version 65?
OK I tested with "65.0.0-pre01" and I confirm the exception is gone, without requiring any change to my code.
What version of the product are you using? Nuget: 63.0.2
What architecture x86 or x64? Both x64 and x86
On what operating system? Win10
Are you using
WinForms
,WPF
orOffScreen
? OffScreenWhat steps will reproduce the problem? In general: Changing the size of a browser and taking then a screenshot from this after the website was loaded again Example: Check out this fork
What is the expected output? What do you see instead? Expected: The size of the bitmap gets updated when I set the size of the browser. Current: The size of the bitmap differs from the size of the browser and therefore causes an AccessViolationException
Please provide any additional information below.
Does this problem also occur in the
CEF
Sample Application from http://opensource.spotify.com/cefbuilds/index.html? Not tested since it looks like the screenshot wrapper method is doing something wrong! Do you want me to test this anyway?