Thanks to visit codestin.com
Credit goes to github.com

Skip to content

.NET 7 - Blazor server app running in VS2022, IIS Express, rapidly consumes all available memory #61605

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.

Sign up for GitHub

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

Jump to bottom
Closed
vsfeedback opened this issue Apr 22, 2025 · 3 comments
Closed

.NET 7 - Blazor server app running in VS2022, IIS Express, rapidly consumes all available memory #61605

vsfeedback opened this issue Apr 22, 2025 · 3 comments
Labels
area-blazor Includes: Blazor, Razor Components Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. Status: No Recent Activity

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.

[severity:I'm unable to use this version] [regression] [worked-in:17.9.7]
As per the title.
Run the Blazor app in VS and even if it sits on a simple razor page that does very little the VS process rapidly consumes all available memory on the computer.

Original Comments

Feedback Bot on 11/18/2024, 03:10 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 3/6/2025, 06:01 AM:

We detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Apr 22, 2025
@dotnet-policy-service dotnet-policy-service bot added the Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. label Apr 22, 2025
@javiercn
Copy link
Member

Thanks for contacting us.

.NET 7.0 is out of support, so as per our support policy we ask you to update to a supported version as a first step (8.0 or 9.0).

In addition to that, please make sure you test your app using the Release environment and without debugging enabled. You'll also have to trigger a Gen 2 compacting GC using GC.Collect as when the GC runs in serve mode it won't release memory unless it needs to (which is not a memory leak).

@javiercn javiercn added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Apr 22, 2025
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Hi @@vsfeedback. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-blazor Includes: Blazor, Razor Components Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. Status: No Recent Activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@javiercn @vsfeedback