ICoreWebView2Environment12

Undocumented in source.
version(Windows && inline_webview2_bindings && all)
interface ICoreWebView2Environment12 : ICoreWebView2Environment11 {
static const
GUID iid;
}

Members

Functions

CreateSharedBuffer
HRESULT CreateSharedBuffer(UINT64 size, ICoreWebView2SharedBuffer* shared_buffer)

Create a shared memory based buffer with the specified size in bytes. The buffer can be shared with web contents in WebView by calling PostSharedBufferToScript on CoreWebView2 or CoreWebView2Frame object. Once shared, the same content of the buffer will be accessible from both the app process and script in WebView. Modification to the content will be visible to all parties that have access to the buffer. The shared buffer is presented to the script as ArrayBuffer. All JavaScript APIs that work for ArrayBuffer including Atomics APIs can be used on it. There is currently a limitation that only size less than 2GB is supported.

Inherited Members

From ICoreWebView2Environment11

get_FailureReportFolderPath
HRESULT get_FailureReportFolderPath(LPWSTR* value)

FailureReportFolderPath returns the path of the folder where minidump files are written. Whenever a WebView2 process crashes, a crash dump file will be created in the crash dump folder. The crash dump format is minidump files. Please see Minidump Files documentation for detailed information. Normally when a single child process fails, a minidump will be generated and written to disk, then the ProcessFailed event is raised. But for unexpected crashes, a minidump file might not be generated at all, despite whether ProcessFailed event is raised. If there are multiple process failures at once, multiple minidump files could be generated. Thus FailureReportFolderPath could contain old minidump files that are not associated with a specific ProcessFailed event. \snippet AppWindow.cpp GetFailureReportFolder

Meta