Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streams in Executable.cs are not disposed #1619

Closed
shrimpy opened this issue Jul 16, 2015 · 3 comments
Closed

Streams in Executable.cs are not disposed #1619

shrimpy opened this issue Jul 16, 2015 · 3 comments
Milestone

Comments

@davidebbo
Copy link
Member

How did you happen to find this? Was it via code inspection, or as a result of catching some leak?

I think you're correct about it, though in practice I'm not sure there are ill effects when dealing with memory streams (since there is no file to close, ...).

@shrimpy
Copy link
Contributor Author

shrimpy commented Jul 20, 2015

right, I am worrying about could potentially cause memory leak

I found it in pull request from @safihamid, where he reference Executable.cs as sample.

@jvano
Copy link
Member

jvano commented Apr 29, 2024

Hi

Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained.
If the problem persists and is related to running on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

This way we can better track and assist you on this case

Thanks,

Joaquin Vano
Azure App Service

@jvano jvano closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants