We're developing a Blazor application on .NET 8 that streams single .jpeg images (200kB) to the browser. Those images could have a frequency of ~1000 images/minute.
We set the images as a base64 encode string in the UI and visualize the app in Chrome.
It seems to be running fine 24/7, if we have enough CPU threads available. It hast been tested on a huge variety of systems. It runs fine, if we have (number of Chrome processes + 1) >= available CPU threads.
But if we have fewer CPU threads, the memory Chrome is using currently increases until it crashes with an out of memory exception.
Even if we reload our page or close it, chrome wouldn't free the memory.
If we would have a memory leak, I would suggest that it occurs independent of the available CPU threads or am I wrong?
Do someone have an explanation, why we are getting this behaviour on hardware with fewer threads?