Blazor project consume all possible memory and server hangs up.
See original GitHub issueIssue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
visual studio mac - Blazor consumes too much Memory
1 Answer. In my case the builder. CloseElement(); was missing. This caused a weird behaviour in the Blazor Application.
Read more >Why does Blazor server app takes away memory while ...
We developed a Blazor server app and is going through testing phase. Our clients have some concern. What we notice is that before...
Read more >RAM usage of .NET Blazor app in Docker container
You can limit the amount of memory that is available to a single container. That way it doesn't consume all the memory on...
Read more >ASP.NET Core Blazor performance best practices
Tips for increasing performance in ASP.NET Core Blazor apps and avoiding common performance problems.
Read more >Dispose of report on blazor server
We determined that DxReportViewer references remain in memory and aren't collected by GC while a Blazor application connection is established.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’ve waited for this mater to get an results from Syncfusion before return to this topic as well, but they turned it into private request where the things start rotating again into endless loop between me and them. Here the topic with example which present the bug. https://www.syncfusion.com/forums/161102/extreme-memory-leaks?fbclid=IwAR0iCSyYeKtvuLCvZlLnmZIxT60H_nzFicMyeB77x-zBILLgYVR1QDEF4lM Here and the screenshot i’ve made with explanations on it.
There is a further development. (which could be useful maybe)
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimalistic repro project (ideally a GitHub repo) that illustrates the problem.