From 21c9ae04585ddcf3642cd62d443c0b858db0adde Mon Sep 17 00:00:00 2001 From: Robert Ly Date: Tue, 10 Apr 2012 16:05:23 -0700 Subject: [PATCH] docs: fix bug 5158332 Change-Id: I4ced8e7808727a6789732d10601fe6aa4985d8ba --- docs/html/guide/developing/debugging/ddms.jd | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/html/guide/developing/debugging/ddms.jd b/docs/html/guide/developing/debugging/ddms.jd index 80b1e476e4187..9892e49f1eece 100644 --- a/docs/html/guide/developing/debugging/ddms.jd +++ b/docs/html/guide/developing/debugging/ddms.jd @@ -128,9 +128,7 @@ parent.link=index.html classes and threads are allocating the objects. This allows you to track, in real time, where objects are being allocated when you perform certain actions in your application. This information is valuable for assessing memory usage that can affect application performance. - If you want more granular control over where allocation data is collected, use the - {@link android.os.Debug#startAllocCounting()} and {@link android.os.Debug#stopAllocCounting()} - methods.

+

To track memory allocation of objects: