BeatPulse UI memory leak

[xabaril]

BeatPulse UI memory leak

[unaizorrilla]

Let me check, I use it on different projects without any issue!
Latest version?

[wormst]

Yes, I'm using latest version (3.0.2).
Initial profiling with dotTrace pointed to UIApiEndpointMiddleware:

[unaizorrilla]

Thanks I try to solve it ASAP!!!

[unaizorrilla]

Hi @wormst

Checkout the code and perform some minor changes, I use dotmemory and I think is ok!, can you check 3.0.2 version of the UI and close this if issue is resolved?

[wormst]

You've probably meant version 3.0.3, but I can't see it available. Could you verify that?
Thanks in advance.

[unaizorrilla]

Hi @wormst

True, Building new package, sorry but i miss add tag!

[unaizorrilla]

On NuGet right now 3.0.3 version

[wormst]

It seems that the issue still appears. You can try adding more liveness to configuration (~10) so the result will be better visible.
Could you try running the project under Visual Studio and watch the Process Memory in Diagnostics Tools if it grows in time?

[unaizorrilla]

I use dotmemory and for me all is ok, I collect different snapshots and the memory consumption is ok in my side, I try to add more liveness and share with you my collection screenshots

[unaizorrilla]

Hi @wormst

I do a new review in the hosted service and change the http client creation. Probably the better option is to use IHttpClientFactory ( I do it on new project, AspNetCore.HealthChecks ) but I don't spend a lot of time improving this project when the new version is already done.

I also check in dotmemory and the project is between 5 MB and 7 MB .NET Memory for a long time, the unmanaged memory is also stable between different executions.

Build is in process the new UI version is 3.0.4

[szogun1987]

Hi. I have prepared PR that reduces memory leak significantly
#99

[unaizorrilla]

Merged #99

[szogun1987]

I have created another PR #101 it should fix memory leaks

[szogun1987]

@wormst @unaizorrilla this issue probably can be closed.