for example the console application is just using around 64k of memory when idle, and will rise to 2MB when running the bigloop. If you are serious about checking for memory, you should follow up on the link provided, as it has really good info about this issue.īut If I look at your code, I see nothing to worry about. If you are interested in some better numbers, don't look at the Process Memory (MB), but select the Memory Usage tab below it, press Take Snapshot and there you can see the amount and types of memory allocated.Įven in TaskManager, your application will have allocated more memory, because of the need to display the console window, and other things. Sadly both of them will not give you an accurate number, and especially the Visual Studio memory will be vastly inflated because it needs a lot of memory for debugging purposes. Judging by the numbers you provided, you have looked at the memory consumption inside VS, and in TaskManager. I finally had some time looking at your issue:ĭetermining the memory usage of an application can be difficult If you don't know exactly what you are looking at. I could throw away the interest and months I spent already in Blazor if only 20 users can use one server at same time I my end app the memory rasie from 88 Mo to 190 in one minute while user does simply zooming / unzooming operation where the math computation is done and call to js interop as well Do I need to consider this as an individual and localized issue having no interest to the community ? I am not sure it's Visual Studio is hiding something and it seems something bad about memory is happening for no obvious reason. What can we conclude if Task Manager show that the exe memory increase like VS already shown. If you want to capture an accurate trace of your program we suggest you follow some of the guidance provided here to accurately measure the memory usage in your app. Consequently, these results are likely not representative of how Blazor behaves in a production environment. When running inside Visual Studio, potentially with the debugger attached, and/or using a debug build, the GC behaves differently.
Posterazor insufficient memory windows 10#
I am using VS2022 Version 17.0.2 under Windows 10 How can I achieve a clean-up startegy when mouse is moving on client browser ? Steps To Reproduce It's easy to call GC.Collect() after 1 million of operation I know after all my readings about this memory subject that memory in general and GC in particular is a whole Universe.but this issue is so big that I'm wondering on stopping this project now before crashing myself on the memory-wall Why is there a so big difference in size allocation ? On console app it raise from 8Mb to 19Mb so it climbs 11Mb. Is it a memory strategy to allocate enough memory for near future supposed use ? Why memory is not released down to its initial value. NetCore version, memory can raise up to 203 Mb and it never goes back to its initial state although the objects are not referenced anywhere else.
Posterazor insufficient memory code#
The Console app is just to have simpliest code ever. 1 million of simple math matrix mulplications then a call to GC.Collect()
The Blazor samples are doing exactly same operation. Then to share with the community, I made one console app and 3 Blazor projects with similar code but targeting different. So I decided to find now the reason why memory was climbing so much and I isolated one code part that seems responsible of part of this memory issue The server would just die before user can finish their work
For one user it's not perceptible, but I can't imagine what it can be with 100 users on a server.
When mouse moves or when wheel moves, some maths computations are done with mouse-coordinates + svg-matrix whenever the mouse is moved to compute coordinates in svg spaceĪnd memory climbs 1Mb after 1Mb to raise rapidly > 100 MB when displaying one single rectangle and memory never goes down. So I decided to investigate why the memory was getting very high and firstly when user was simply moving the mouse in area I have started a Blazor (server-side) svg-editor ambitious project and I'm facing very very high memory consumption (more than 500 Mb for some svg)
0 kommentar(er)
