RDM v2022.3.xx is generating tons of MSEdgeWebView processes, swallowing all the resources
Hello,
On wednesday, I installed v2022.3.15.0 (upgraded from v2022.2.29.0) on 2 different PCs (Win10 and Win7), and the result is CATASTROPHIC on both !!!
As soon as launched, RDM also launches tons (more than 50 !) msedgewebview2 processes till the whole RAM (16GB !) is filled...
And of course, RDM is totally unresponsive ! Also unable to end it properply (the RDM process needs to be killed, as well as all webview processes).
This morning, I upgraded v2022.3.15 to v2022.3.16. Still the same.
With v2022.2.xx, there was also some (a dozen) msedgewebview processes, but none was swallowing RAM and processor resources...
RDM is simply now putting my computers on the knees...
Please, help !
PS: MS Edge WebView runtime v107.0.1418.35 installed
Hello,
I'm unable to reproduce or even explain why this is happening in your environment. Could you verify if you have anything strange in the application logs located in Help? You could also verify the Event Viewer and finally do you have anything special in your environment (Insider Preview, Terminal) that could help me diagnostic the problem?
Could you try to uncheck those settings to see if this reduce the number of process you get?
Regards
David Hervieux
Hello David,
I don't understand either !
I have RDM on 4 PCs, 3 under Win10, 1 under Win7, all different models of Dell PCs.
I have many administration tools installed for the management of my network.
No errors in Windows event logs.
I can't open the diagnostics logs under the help menu, because RDM becomes unresponsive quite immediately it's opened !
I've managed with grain pain to enter the options window, and went into MS Edge section to uncheck the 4 options as asked. No change after restarting RDM.
It generates exactely 52 msedgeview2 processes each time it's launched (about 15s after RDM startup, the 52 edge processes are there and it's finished, all I can do is to kill RDM and edgeview).
As RDM is an absolute necessity, I've uninstalled v2022.3 from my main Win10 PC, and reinstalled the old v2022.2.29 back instead, and everything's fine again ! Fortunately.
But I really don't know what's happening with this new v2022.3...
If the issue was happening only on 1 PC, I could say there's something wrong with that one, but actually, the issue exists on all the 4 PCs equiped with RDM !
That's why I think there's a problem with RDM.
Best regards,
Could you verify the application log but from RDM 2022.2? You might see something?
Regards
David Hervieux
Hello David,
It was a bit complicated, but I finally managed to get some logs from within RDM v2022.2.
The name of the log database also changed from v2022.2 to v2022.3 (there's a "64" at the end of the name of the file in v2022.2 with isn't there in v2022.3), so I had to cheat and swap the files so that RDM 2022.2 could open the 2022.3 log file.
I'm joining the zipped text-exported log file to the thread, so that you can analyze it, because indeed, there's a lot of errors...
Best regards,
Hello,
I don't understand this error:
[02-11-2022 00:59:05 - 2022.3.15.0 - 64-bit] Erreur: System.Reflection.TargetInvocationException: Une exception a été levée par la cible d'un appel. ---> System.Reflection.TargetInvocationException: Impossible d'obtenir le handle de fenêtre pour le contrôle 'EnhancedWebBrowser'. Les contrôles ActiveX sans fenêtre ne sont pas pris en charge. ---> System.ComponentModel.Win32Exception: Erreur lors de la création d'un handle de fenêtre.
It's an error with the legacy Webrowser. I've made a potential fix.
Regards
David Hervieux
Hello,
How will that fix become available ?
Through a new release (v2022.3.0.17) ?
Best regards,
Hello,
The version that contains this fix has just been released, it can be downloaded using the link below:
https://devolutions.net/remote-desktop-manager/home/thankyou/rdmsetup
Let us know if it works for you.
Best regards,
James Lafleur
Hello,
I downloaded and installed this new v2022.3.0.18 on my old Win7 PC (I now use that one for RDM tests, so I can keep a working v2022.2 on my prodution PC).
Still the same !
52 msedgewebview2 processes created just after RDM startup, and the CPU and RAM resources got totally used in a minute.
Worse: this time, the log database was not modified ! There's no entry for v2022.3.0.18 at all.
Best regards,
Hello,
That's a bad news. I will go back to the drawing board and try something else. I have another idea.
Regards
David Hervieux
Could you try this build?
https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2022.3.19.0.exe
Regards
David Hervieux
Could you try this build?
https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2022.3.19.0.exe
Regards
Hi, I'm having this issue as well. It persists with 2022.3.19.
Any logs?
David Hervieux
Any logs?
Hi David,
Is there a way to get the logs outside of the application? The app becomes unresponsive as soon as I launch it.
-Josh
Could you try this build?
https://cdn.devolutions.net/download/Setup.RemoteDesktopManager.2022.3.19.0.exe
Regards
Hi, I'm having this issue as well. It persists with 2022.3.19.
Hi,
The same for me !
Absolutely no change with v2022.3.19...
As for Josh, RDM is unresponsive as soon as it is launched and must be killed in order to recover a usable computer.
The msedgewebview processes must also be killed, but sometimes, killing RDM makes them stop by themselves.
Hello,
I will try to build a small application to reproduce the issue. I them meantime could you try to unzip RDM 2022.3.18 in another folder and execute it Side By Side. Just try a simple SQLite data source and let me know if you can start the application.
Regards
David Hervieux