JuliaLang / JuliaLang/Distributed.jl
need periodic distributed GC for quicker release of remote objects
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 55
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Overwriting RemoteRef variables does not release memory.
Start Julia from bash: julia -p 2
Check memory: free -m (used = 7398)
In Julia: r = remotecall(2, rand, 17000, 17000);
Check memory: free -m (used = 9617)
Now overwrite r:
In Julia: r = remotecall(2, rand, 17000, 17000);
Check memory: free -m (used = 11834)
In Julia: gc()
Check memory: free -m (used = 11814)
I would expect the overwritten r to have its memory released by the garbage collector.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the memory behavior with julia -p 2, remotecall, and gc() as described. Start by tracing how overwritten RemoteRef values are handled, then define and implement periodic distributed cleanup so remote objects are released; done means the reproduction no longer retains the overwritten allocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100