Home
last modified time | relevance | path

Searched refs:leak (Results 1 – 13 of 13) sorted by relevance

/frameworks/base/libs/hwui/tests/unit/
Dmain.cpp70 for (auto& leak : info.leaks) { in logUnreachable() local
71 if (addrs.find(leak.begin) == addrs.end()) { in logUnreachable()
72 merged.leaks.push_back(leak); in logUnreachable()
74 merged.leak_bytes += leak.size; in logUnreachable()
75 addrs.insert(leak.begin); in logUnreachable()
/frameworks/base/core/java/android/app/
DLoadedApk.java883 IntentReceiverLeaked leak = new IntentReceiverLeaked( in removeContextRegistrations() local
888 leak.setStackTrace(rd.getLocation().getStackTrace()); in removeContextRegistrations()
889 Slog.e(ActivityThread.TAG, leak.getMessage(), leak); in removeContextRegistrations()
891 StrictMode.onIntentReceiverLeaked(leak); in removeContextRegistrations()
911 ServiceConnectionLeaked leak = new ServiceConnectionLeaked( in removeContextRegistrations() local
914 leak.setStackTrace(sd.getLocation().getStackTrace()); in removeContextRegistrations()
915 Slog.e(ActivityThread.TAG, leak.getMessage(), leak); in removeContextRegistrations()
917 StrictMode.onServiceConnectionLeaked(leak); in removeContextRegistrations()
/frameworks/base/core/java/android/view/
DWindowManagerGlobal.java423 WindowLeaked leak = new WindowLeaked( in closeAllExceptView() local
426 leak.setStackTrace(root.getLocation().getStackTrace()); in closeAllExceptView()
427 Log.e(TAG, "", leak); in closeAllExceptView()
/frameworks/base/location/lib/
DREADME.txt30 API that does not leak the internal classes.
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Dstopping.jd80 you use {@link android.app.Activity#onStop()} to release resources that might leak memory.</p>
186 last chance to clean out resources that could lead to a memory leak, so you should be sure that
Dstarting.jd267 potentially leak memory if not properly closed, you should kill them during {@link
/frameworks/base/docs/html/training/contacts-provider/
Dretrieve-details.jd267 leak. For example:
Dretrieve-names.jd494 recycle the {@link android.database.Cursor}, which causes a memory leak. For example:
/frameworks/base/docs/html/guide/topics/resources/
Druntime-changes.jd128 leak all the views and resources of the original activity instance. (Leaking resources
/frameworks/base/docs/html/training/articles/
Dsecurity-tips.jd210 <p>Do not leak permission-protected data. This occurs when your app exposes
408 could inadvertently leak user data to other applications.</p>
Dmemory.jd195 it's actively performing a job. Also be careful to never leak your service by failing to stop it
/frameworks/base/docs/html/guide/topics/ui/
Dmulti-window.jd587 app doesn't crash or leak memory. For information about checking your app's
/frameworks/base/docs/html/topic/libraries/support-library/
Drevisions.jd735 <li>Fixed a memory leak in
1036 <li>Fixed a memory leak that occurs when tinting drawable resources using