Skip to content

[wasm] report undisposed proxies of JSObject, ManagedObject #70660

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

Closed
pavelsavara opened this issue Jun 13, 2022 · 2 comments
Closed

[wasm] report undisposed proxies of JSObject, ManagedObject #70660

pavelsavara opened this issue Jun 13, 2022 · 2 comments
Assignees
Milestone

Comments

@pavelsavara
Copy link
Member

pavelsavara commented Jun 13, 2022

Add runtime feature to report undisposed proxies of JSObject, ManagedObject so, that the developers could find on which instances they need to call dispose() explicitly, if they don't want to rely on finalizers. Both JS and C# proxies.

@pavelsavara pavelsavara added this to the Future milestone Jun 13, 2022
@pavelsavara pavelsavara self-assigned this Jun 13, 2022
@ghost
Copy link

ghost commented Jun 13, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Add runtime feature to report undisposed proxies of JSObject, ManagedObject so, that the developers could find on which instances they need to call dispose() explicitly.

Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript

Milestone: Future

@pavelsavara
Copy link
Member Author

This is fixed by #88052

@pavelsavara pavelsavara modified the milestones: Future, 8.0.0 Jul 26, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant