Azure Functions PS + EXO V3 -- Possible memory leak? about azure-functions-powershell-worker HOT 5 CLOSED

Hello @iyerusad -- Could you please open a support case via the Azure Portal? We will need to collaborate with the ExchangeOnlineManagement team to help them gather any telemetry they need from our worker VMs, so that they can investigate and resolve this issue. Thank you.

/cc @chrisda @AnatoliB @shreyabatra4

from azure-functions-powershell-worker.

I will go ahead and close this issue.

from azure-functions-powershell-worker.

I am unable to create a Support Request via Azure Portal because it only allows me to create support requests for Billing, Subscription Management, and Quota increase... this appears to be a Bug/Technical Issue. In the EXO V3 repo issue I documented some more troubleshooting and it appears to crash like clockwork at 16 runs.

Is there a way to report this likely bug? Azure Portal or elsewhere? I have attempted to report in this repo, in the EXO V3 repo, and both point to Azure Portal who wants me to upgrade our tenant to $29/m to report a Technical issue.

from azure-functions-powershell-worker.

Hello @iyerusad -- Could you please check to see if you have any supports plans under
Help + support - Microsoft Azure. If not, you might need to sign up for a Developer Support which start from $29 a month. For this, your tenant admin should be able to help. Thank you.

from azure-functions-powershell-worker.

It appears dotnet.exe bloats to fill memory capacity and doesn't release. You can repro this locally (not Azure) by running same code until it eats up all the machine RAM. Just tested locally and with 30 runs dotnet.exe has bloated to 5.194GB and will fill out my devbox's RAM until it fails too or I kill the process.

Azure Functions Core Tools
Core Tools Version: 4.0.5198 Commit hash: N/A (64-bit)
Function Runtime Version: 4.21.1.20667

from azure-functions-powershell-worker.