ActivityLeakFixer中drawable应该尽快清除native层引用的bitmap对象 #666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
在这里回收 Bitmap 不安全，无法保证 Bitmap 没有在其他地方用到 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ActivityLeakFixer作为内存泄漏兜底，应该清除drawable的同时也应该清除bitmap，因为bitmap在native层还是内存还是有一定的消耗，等待gc执行不太符合内存泄漏急需释放内存的场景，所以应该调用bitmap的recycle方法通过bitmap机制去清除native层引用。