I am not sure if I understand your question. The short answer is you can NOT copy WebView1's state to WebView2.

However session data such as log in sessions, may not be part of the WebView so in that case they do not need to be copied. For example, if you have logged in through WebView1 and it has created a persistent login cookie, then WebView2 will see this cookie when it loads resource from the same site. This works because the cookie storage is not part of WebView's state data. It's a storage that shared by all WebViews managed by the same browser engine instance.

Other information such as a WebView's scrolling offset, or the current value of a textbox, are strictly maintained by the WebView itself. There is no built in support for you to copy such state data directly to another WebView. It is possible for you to use JavaScript to fetch these values from WebView1 and then use some other JavaScript code to set this values in WebView2. However that will need to be done by your code. Once you have the correct JavaScript code, you can call WebView.EvalScript to run the script.

There is no such thing as "reuse" between different WebViews. If you want WebView2 to display the same page as WebView1, you load the same Url into both WebVi8ews.

You can't do it this way. The load will not finish unless you are running a message pump. You would typically use a thread runner to resolve this issue:

https://www.essentialobjects.com/doc/webbrowser/start/webview_no_ui.aspx

Additionally, it's very likely that your resize and capture will fail on a size of 5000 * 4000. For performance reason, internally the browser engine uses hardware acceleration surface support provided by the video card/driver to compose the final output whenever it can. Since the primary purpose of such composition is for screen output, the GPU hardware and drivers usually do not maintain buffers that are significantly larger than a normal screen size, which means resizing the browser window to this size can often fail.

In your case, you can try to use this overload of Capture to capture the screen:

https://www.essentialobjects.com/doc/eo.webbrowser.webview.capture_overload_1.aspx

There are two key points about this function:

1. The captured area does not have to be the same as the screen area. This means you do NOT need to resize the WebView to cover the entire area you want to capture. The capture area is specified by the first argument of this method. The WebView size is not directly related to the capture area --- however it can affect the layout of the page. For example, if you have text that automatically wrap to the next line, then obviously a narrower window will produce more text lines;

2. The final image size is specified in the second argument. Typically this size can be used to scale down the size of the final image to avoid buffer allocation failure. For example, you can specify the capture area to be 5000 by 4000 but the final image size to be 500 by 400. This will significantly reduce the output image size thus make the call more likely to succeed. If you wish to have high resolution output, then you have two options:

a. Capture a smaller area. This is due to the same memory restrictions (not directly related to how much memory your system has but more to internal implementation of your GPU hardware/driver);
b. Use our HTML to PDF feature to render the page to PDF. PDF is rendered in vector format instead of bitmap. So it can maintain high quality and reasonable size at the same time (this is exactly why PDF is so popular). This option might work better for your purpose because PDF usually offers the best viewing quality since you can zoom in without losing quality;

Hope this helps. Please feel free to let us know if you still have any questions.

Thanks!