Question about IStream-Behavior of ICoreWebView2WebResourceResponse::get_Content

[Urmeli0815]

Hello,

in our app we use the IStream returned by ICoreWebView2WebResourceResponse::get_Content to serve files to WebView2.

Because of the structure of our app we serve a huge JS-File (ca. 30MB). For developers we additionally serve the source map for the JS-File (~ 80MB) in the same request as an embedded source map. This means we write approx. 110MB to IStream.

We still have an x86-Variant for our app and there we now encounter Out-Of-Memory-Exceptions in EmbeddedBrowserWebView.dll. It seems that everything that is written to IStream is accumulated in EmbeddedBrowserWebView.dll code and only when the request is finished the data gets sent to the other WebView2 process. (btw: the x64-Variant works fine, memory allocation doesn't seem to be a problem there).

With that it doesn't seem to make a difference if I write the 110MB in smaller chunks as the accumulation of the data still happens in EmbeddedBrowserWebView.dll.

Can you elaborate if this analysis is correct and if there is any way to write such huge response data?