Support

Dear Team,

I’m using the Beta 2.5.3 with Edge designer in VS2019 (16.10.4)

After some time, under certain conditions I’m starting to see 100 instances of msedgewebview2.exe and the VS becomes slow.

Restarting VS usually helps.

Please tell me if I can send you the logs for you to see who keeps the instances.

C:\Users\<username>\AppData\Local\Temp\Wisej2\WebBrowserRendererEdge\EBWebView

Regards,

Kizaemon.

Attachment

- Kizaemon Date
- Jul 29, 2021 - 5:35 pm
P.S. “Recycle All” does not recycle all instances. Several will be closed indeed, but some are remaining running. The VS designer is still slow. Only full restart of VS helps.

You can reduce parallel renderers as a temporary workaround and how many instances of Visual Studio did you start when using “Recycle All”?

Kevin (ITG)

- Kizaemon Date
- Jul 29, 2021 - 10:57 pm
Thank you — I’m running only one instance of VS with 2 renderers. Everything works well, until some condition met. I’ll try to see if I can reproduce the conditions. (e.g. multiple designer windows open, my custom controls, mixin themes, …)
- Levie (ITG)
- Jul 30, 2021 - 5:01 pm
Hi Kizaemon, we’re still working on reproducing the issue. Can you please try adding Computer\HKEY_CURRENT_USER\SOFTWARE\IceTeaGroup\Wisej 2\Designer\RendererPoolDisposeInterval=3000 (DWORD) to the registry? This lowers the timeout interval for the excess renderers to be cleaned up and disposed. The default value is 60,000 (1 minute). Best, Levie
- Levie (ITG)
- Aug 3, 2021 - 5:25 pm
Hi Kizaemon, I also wanted to let you know we added a new enhancement that should reduce the amount of memory used by pooled renderers. The msedgewebview2 instances will go from ~27mb each to ~2mb each when they’re not being used. It should be available in the next beta build for you to try. HTH, -Levie

Beta 2.5.3 -- multiple msedgewebview2.exe instances