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

Possible memory leak when service is running #24

Closed
tylermzeller opened this issue May 4, 2017 · 3 comments · Fixed by #26
Closed

Possible memory leak when service is running #24

tylermzeller opened this issue May 4, 2017 · 3 comments · Fixed by #26

Comments

@tylermzeller
Copy link
Collaborator

Steps to reproduce:

  • Open up client, and make sure service is running

  • Make sure server is not running. If it is, close it down to ensure no processing on the client is happening.

  • Open the Android monitor and select the crowd-ml:datasend process. View the allocated memory continuously increasing in the performance profiler.

This may be due to the wifi listener, because that is the only running thread in the :datasend process.

@3ygun
Copy link
Collaborator

3ygun commented May 9, 2017

Is this in the tensorflow branch?

@tylermzeller
Copy link
Collaborator Author

No, I can view it on master.

@3ygun
Copy link
Collaborator

3ygun commented May 9, 2017

Was able to reproduce.

3ygun added a commit that referenced this issue May 10, 2017
Following the https://stackoverflow.com/questions/1783117/network-listener-android and https://developer.android.com/reference/android/net/ConnectivityManager.html I changed from the custom WiFi ready code to an event listener one. Appears to work tested turning on and off the WiFi on my phone and the app didn't crash and was able to resume calculations. Also seems to resolve #24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants