[Bug report 4][Unnecessary Persistence of Microsoft Edge WebView2 Subprocesses in cTrader Desktop]
[Bug report 4][Unnecessary Persistence of Microsoft Edge WebView2 Subprocesses in cTrader Desktop]
01 Jan 2025, 22:51
Hi,
1. Context and problem:
Environment: Windows 10
1.1 When launching cTrader Desktop version 5.1.11.36230 with the "Trade" menu active, only one cTrader process is displayed in Task Manager, which is expected behavior.
1.2 Switching to the "Algo" menu activates 7 instances of Microsoft Edge WebView2 (msedgewebview2.exe) as subprocesses under the cTrader Desktop application in Task Manager. These instances consume memory resources.
1.2.1 It appears that the presence of the "Tutorial" panel, which includes a YouTube video (which I did not even play), triggers these WebView2 subprocesses. Allocating only one subprocess for this panel seems reasonable.
1.2.2 However, it remains unclear whether other parts (as seen in the image below) of cTrader Desktop also require these Microsoft Edge WebView2 subprocesses to justify their existence.
1.3 Returning to the "Trade" menu does not terminate the 7 instances of Microsoft Edge WebView2 subprocesses, even though the "Tutorial" panel is no longer visible. This behavior seems inconsistent and unnecessary.
1.3.1 Why do these Microsoft Edge WebView2 subprocesses persist after navigating away from the "Algo" menu ?
1.3.2 Could this be a bug ?
2. Proposed solution:
The Microsoft Edge WebView2 subprocesses should be terminated automatically when they are no longer needed. For instance:
- Upon switching back to the "Trade" menu, the Microsoft Edge WebView2 subprocesses should be evaluated and terminated if no active panels or other parts require them.
- This optimization would reduce unnecessary memory consumption and improve overall application efficiency.
3. What do you think about this bug / topic ?
Thank you for considering this request and I’m happy to provide additional details or insights if needed.
firemyst
02 Jan 2025, 01:23 ( Updated at: 02 Jan 2025, 07:07 )
It's an issue, and a similar one was already raised in the forums.
You can read their response here:
https://community.ctrader.com/forum/ctrader-support/43951/
In a nutshell, they weren't going to look into it.
@firemyst