suggest change




Loader is good choice for prevent memory leak if you want to load data in background when oncreate method is called. For example when we execute Asynctask in oncreate method and we rotate the screen so the activity will recreate which will execute another AsyncTask again, so probably two Asyntask running in parallel together rather than like loader which will continue the background process we executed before.


Class | Description | —— | —— |LoaderManager | An abstract class associated with an Activity or Fragment for managing one or more Loader instances. |LoaderManager.LoaderCallbacks | A callback interface for a client to interact with the LoaderManager.Loader | An abstract class that performs asynchronous loading of data. |AsyncTaskLoader | Abstract loader that provides an AsyncTask to do the work. |CursorLoader | A subclass of AsyncTaskLoader that queries the ContentResolver and returns a Cursor. |


Introduced in Android 3.0, loaders make it easy to asynchronously load data in an activity or fragment. Loaders have these characteristics:

When not to use Loaders

You shouldn’t use Loaders if you need the background tasks to complete. Android destroys Loaders together with the Activities/Fragments they belong to. If you want to do some tasks, that have to run until completion, do not use Loaders. You should use services for this kind of stuff instead.

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents