apple / apple/swift-distributed-actors
Investigate and break strong reference cycle to ActorSystem
Open
1 - triaged
2 - pick next
kind/bug
memory leak
- Dominant language
- Swift
- Stars
- 677
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
Normally "not an issue" since there is 1 system per application, however we must not willingly cause leaks even if people did something weird like spawning and stopping tens of systems -- e.g. it shows up in tests where the systems are not released.
Contributor guide
Research direction
Start by reproducing the reported test scenario: spawn and stop tens of ActorSystems and verify whether they are released. Trace references involving ActorSystem to identify the cycle; done means the cycle is broken and the systems are released without regressing actor behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100