Memory goes through the roof untill all memory (8GB) is consumed. I also noted that the hour glass icon with "Loading cmdlets metadata...." never completes.
The metadata loading time and the amount of memory to be consumed depends on the number and size of the PowerShell modules installed on the computer where Adaxes service runs. You can uninstall redundant modules from the computer to decrease the memory leaks.
I presume Adaxes is attempting to get metadata from powershell to help with syntax while editing etc?
The presumption is correct.
Yes it maybe a powershell problem however it would appear it has something to do with how adaxes is interacting with Powershell - Please dont just state powershell issue and whipe your hands of the issue.
Adaxes just requests metadata of PowerShell modules from operating system. Once the request is sent, there is no possibility to cancel it. Currently, the only way to prevent the issue is to not send the request. However, we are looking for a workaround.
What i have noticed is it appears that the adaxes service is repeatitively trying to read a ProxyCmdletDefinitions.ps1 file for MS Graph?
MS Graph is just one of the modules whose metadata is loaded on opening PowerShell Script Editor. There is no additional relation between the module and the issue.