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

background service unresponsiveness after being open for a while #1207

Open
10 tasks
jemsurfer opened this issue Jul 21, 2021 · 0 comments
Open
10 tasks

background service unresponsiveness after being open for a while #1207

jemsurfer opened this issue Jul 21, 2021 · 0 comments

Comments

@jemsurfer
Copy link

jemsurfer commented Jul 21, 2021

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

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
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

1 participant