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

Investigate potential memory leak associated with the use of deferred nodes. #692

Open
willow-ahrens opened this issue Jan 7, 2025 · 2 comments
Assignees

Comments

@willow-ahrens
Copy link
Collaborator

Deferred nodes now hold copies of the actual inputs, for use in the galley scheduler. If we hold on to the program with deferred nodes, we may introduce a memory leak as the inputs cannot be garbage collected.

@wraith1995
Copy link
Collaborator

Does Julia have weak references? That would be the typical solution to this problem.

@willow-ahrens
Copy link
Collaborator Author

I think the main issue is that we still hold on to the program, and the inputs are now pasted into the program. The inputs currently remain reachable as the programs are keys in the compiled code cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants