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.

Sign up for GitHub

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

Jump to bottom

Shutting down Kaku's service does not completely kill the service #13

Open
0xbad1d3a5 opened this issue Feb 17, 2019 · 1 comment
Open

Shutting down Kaku's service does not completely kill the service #13

0xbad1d3a5 opened this issue Feb 17, 2019 · 1 comment
Labels
backlog bug

Comments

@0xbad1d3a5
Copy link
Owner

0xbad1d3a5 commented Feb 17, 2019 •
edited
Loading

Not sure if this is just Android behavior or not with services. But onDestroy does get called and I'm pretty sure I'm disposing of every object properly. Regardless, this is causing us to leak a little bit of memory each time this happens. After 40+ open/close cycles in rapid succession it starts to affect system performance.

Force stopping the Kaku service through Android's Apps screen / service screen will reclaim lost memory and return performance back to normal on the device though.
@0xbad1d3a5
Copy link
Owner Author

Tested this again last night. Surprisingly wasn't able to repo the issue anymore...

Will probably try again to repro a couple times before closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@0xbad1d3a5