This repository has been archived by the owner on May 26, 2022. It is now read-only.
Stop resolver and query when no longer needed #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
DNSSDBindable
in my app, I usedDNSSDActivity.java
as a guide. I found that lots and lots of threads were being created, but never destroyed. This was leading to performance issues and occasionalOutOfMemoryError
exceptions.I followed your recommendation here regarding stopping
resolve
andquery
when no longer needed, and the issue with numerous threads has been fixed.This pull request updates the example app with this recommendation.