background service unresponsiveness after being open for a while
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
## The Issue
The background service and app are glitchy, unresponsive and refuse to close after a few days of being open. The only way to close the app is to restart
### Steps to reproduce
1. Open LBRY app, with all options under the 'other' section in settings turned on. (Including 'participate in data network')
2. Leave the service open in the background and perform usual phone tasks
3. See the difference in performance after a few hours from when the app was started
### Expected behaviour
Performance and behaviour stays the same reguardless of uptime
### Actual behaviour
Service becomes unresponsive and glitchy, menus related with accounts (channels, wallet, rewards, library, publishes, invites) refuse to open 'the background service is still initializing..', despite being open for hours. All other menus open and work fine including video playback.
## System Configuration
- Device: Samsung galaxy s10+
- Android version: Android 11, kernel 4.14.113-2164494
- Build number: RP1A.200720.012.G975FXXBFUF3
## Anything Else
- Phone uptime at time of writing is 80hr 30mins
- I know that it's bad practice to not reboot a phone every 2 days or so, but a background process should be fail-proof
## Screenshots
## Internal Use
### Acceptance Criteria
1.
2.
3.
### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed
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
Start by reproducing the issue on the listed Samsung Galaxy S10+ and Android 11 configuration, leaving the LBRY app and background service open while checking the account-related menus. Investigate the background service behavior after extended uptime; done means the service and app remain responsive and those menus open normally without requiring a phone restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100