1. Blazor Server, .NET 10, EF Core 10, PostgreSQL, Radzen Blazor 8.7.3
2. Only 1 table is used.
3. All code is generated by Radzen Blazor Studio without any modifications.
4. Publish in Release mode and deploy to Ubuntu.
5. Monitor the memory usage of the Blazor Server app every 2 seconds on Ubuntu.
6. Switch back and forth between the Home and ItemMasters pages.
7. The memory usage of the Blazor Server app continuously increases, indicating a memory leak somewhere.
8. Why did I perform this test? Because my production environment deployed at a client’s site crashed. The reason was that multiple clients were switching pages, causing the Blazor Server memory to keep increasing, with the app using up to 3.5GB of memory.
9. I cannot determine the exact cause, which is why I conducted this test!
