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

What about the performance of the listview with large number of items? #13

Closed
jaydeepw opened this issue Jan 23, 2015 · 2 comments
Closed

Comments

@jaydeepw
Copy link

Calling

TextDrawable drawable = TextDrawable.builder()
.buildRect("A", Color.RED);

continuously in any AdapterView will exhaust the app out of memory.
How will this be handeled?

@amulyakhare
Copy link
Owner

According to my understanding, creating new drawable instances in the AdapterView will not result in the application going out-of-memory. Since ListView will recycle views, when the setImageDrawable(drawable) is called, it will clear the reference to the old drawable (which will eventually get garbage collected). Can you elaborate, why do you think the application memory will be exhausted?

@jaydeepw
Copy link
Author

True. The app will not run out of memory but it will require the app to increase the frequency of GC calls.
So, I guess, we can say it is optimized for listview or RecyclerView.

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

2 participants