thunderbird / thunderbird/thunderbird-android
Close all open connections when abandoning a Backend instance
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
When BackendManager.getBackend() is called after server settings have been changed the old Backend instance is abandoned and a new one is created with the current server settings. This keeps all connections associated with that old Backend instance open until it is garbage collected.
We should add a Backend.shutdown() method to release all resources that can be invoked when the instance is abandoned.
Contributor guide
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
Start at BackendManager.getBackend() and trace how the old Backend instance is replaced after server settings change. Implement the requested Backend.shutdown() resource-release path and invoke it when the old instance is abandoned. Done means connections associated with the abandoned instance are closed without waiting for garbage collection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100