wangsong-ms

I could not repro this issue in 122.0.2365.92 on my end. @neo42deg would you mind to upload your sample app?

Thanks. I can repro the issue with the app you uploaded. But not in [WPF sample](https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2WpfBrowser) with the runtime you provided. There might be some gaps in BlazorWebView. This issue...

Hi @rasec8711 I couldn’t reproduce the issue. It’s possible that my testing env is on Windows 11 where Quick Access folder has been removed from the left navigation pane. And...

@rasec8711 Hi! Is there any update?

Hi, @ztextplus can you explain more about feature1/feature2? Are they created from same ICoreWebView2 with child `iframes`? Like ``` [main frame [child_iframe1: feature1], [child_iframe2: feature2], [child_frame...:] ] ``` FYI, `IFrameMemoryUsage`...

I don't think this API support your case. There're different cases one browser have many renderer process. This api will support only iframe case, which you create iframes inside that...

Hi @ztextplus, You can check [GetProcessExtendedInfos](https://learn.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2environment13?view=webview2-1.0.2478.35#getprocessextendedinfos)(C++) API, which provides the mapping between renderer process Id and associated frame Info. And each `ICoreWebView2`/`ICoreWebView2Frame` has the `FrameId` property now, so you should...

@dfghj44444 Do you mean `CoreWebView2ProcessKind`? Here's the C++ API reference [ICoreWebView2ProcessInfo](https://learn.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2processinfo?view=webview2-1.0.2535.41#get_kind)

Hi @dfghj44444 The [GetProcessExtendedInfos](https://learn.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2environment13?view=webview2-1.0.2478.35#getprocessextendedinfos) API enables you to retrieve all renderer processes info with associated frame info including main frame and all sub-frames. To group sub-frames under their respective main...

Thanks for reporting! I was able to reproduce it and added it to our backlog for further investigation.