Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor IJSRuntime.Invoke memory leak problem #46761

Closed
1 task done
YJFu-Bifrost opened this issue Feb 20, 2023 · 1 comment
Closed
1 task done

Blazor IJSRuntime.Invoke memory leak problem #46761

YJFu-Bifrost opened this issue Feb 20, 2023 · 1 comment
Assignees
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-jsinterop This issue is related to JSInterop in Blazor feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Comments

@YJFu-Bifrost
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

in my project I use mass IJSRuntime.Invoke to draw canvans, the performance is good but will happen memory leak. I tracked memory change but memory occupy is not happen in my code. I really sure it's happened at lowaer layer. please solve this issue. thanks.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

dotnet --version 7

Anything else?

No response

@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly feature-blazor-jsinterop This issue is related to JSInterop in Blazor labels Feb 20, 2023
@MackinnonBuck
Copy link
Member

It's possible that you're seeing an increase in memory use because of how much data is being JSON-serialized for JS interop. If this is a Blazor WebAssembly app, you might see performance improvements by using the new JSImport-based interop. If this is a Blazor Server app, I would recommend taking a look at this issue to see if the insight there is useful.

We're going to close this out because we don't believe there is an issue in the framework. If you continue to experience the issue and believe it is indeed a framework bug, please submit another issue with a minimal repro project that demonstrates the issue, hosted as a public GitHub repository. Please also provide any diagnostic information you've collected that clearly shows the memory consumption problem you describe. Thanks!

@MackinnonBuck MackinnonBuck closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-jsinterop This issue is related to JSInterop in Blazor feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Development

No branches or pull requests

3 participants