aloubert

Hello,

v2022.3.22 also works for me now !

Thanks David.

Regards

No, recreating the whole database is far too much work !

I have dozens of remote sessions defined...

Indeed, being able to reproduce the issue on your side will be helpful for you to find out what's happening...

Regards

Could you send me the working and non working cfg for a compare? Don't worry there is no sensitive data in it but you can send it as private message still.

Regards

Hi,

Here are 2 config files:

• The original v2022.3 (with a SQLite DB) working config.

• The v2022.2 config, working in v2022.2 but not once imported in v2022.3

Regards,

Hello,

It's interesting. Perhaps it's a setting the cause the issue. Could you try to import and export your data source configuration (not the data) in the unzipped RDM. By the way, when RDM is not installed in Program Files, the cfg and WebView cache is in the installation folder.

Regards

Hello,

Here are some results:

• With RDM 2022.3 unzipped in a standalone folder, and an empty SQLite connection database: startup and functions are OK.

• I then exported its original config to save it. After that, I imported the config coming from RDM 2022.3 installed by the setup and freezing. RDM unzipped is then ALSO freezing (and of course, the ton of msedgewebview processes are also present) !

• I finally imported the originally saved config back into the unzipped RDM, and RDM works again...

Clearly, it must be something in the config that creates the issue, but what ?

I also tried deleting the RDM Egde cache folder from the setup-installed RDM.

As soon as RDM is started, the cache folder is recreated, but RDM still freezes and the edgewebview processes keep generating.

The cache folder mightn't seem to be responsible ?

PS: I managed to catch some errors from the unzipped RDM. I don't know if it can help, but here it is, post-joined...

Regards,

Hello,

1) The test "webviewtest" app works ! I've launched it, the Devolutions start page appears, I can navigate in it, and CPU and RAM resources are OK.

2) I've unzipped RDM 2022.3.18 in a separate folder. I've also launched it successfully with the default empty Connections.db SQLite database. No resource issue, the application is responsive...

Could our issue come from the contents of our connections database ?

Best regards

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 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,

How will that fix become available ?

Through a new release (v2022.3.0.17) ?

Best regards,

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 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,

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 installed v2022.3.15.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 !

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 !