Skip to content

Debug and fix memory leaks #20

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.

Sign up for GitHub

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

Jump to bottom
Open
2 tasks
ammarahm-ed opened this issue Mar 15, 2025 · 0 comments
Open
2 tasks

Debug and fix memory leaks #20

ammarahm-ed opened this issue Mar 15, 2025 · 0 comments

Comments

@ammarahm-ed
Copy link
Collaborator

ammarahm-ed commented Mar 15, 2025 •
edited
Loading

New runtimes work differently and are not well tested yet for memory leaks. We are working on fixing issues anything we find.

  • When a java object is finally freed in Java, we notify the JS side to free the JS counterpart. At this time, the Java object is held weakly in Java too using a WeakReference. While the Java object is weakly held, the WeakReference is strongly kept in a HashMap never getting removed. In this PR we release the WeakReferences too on GC event ensuring that all memory is reclaimed. Fixed in 5e48302
  • Investigate Java Interface Implementation leaking on JS Side
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ammarahm-ed