From 634caa4ebc4e6175e9d70d9e7a4e0414848aab79 Mon Sep 17 00:00:00 2001 From: Dan Dascalescu Date: Thu, 18 Feb 2016 13:36:13 -0800 Subject: [PATCH] docs: Fix typo "remove allocations for" and "else where" bug: https://code.google.com/p/android/issues/detail?id=26319 While at it, fixed "else where" in the paragraph above. Change-Id: I2cd5781ed84a4c2570762ddcbe52ab047fb0bd39 --- docs/html/tools/debugging/debugging-memory.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd index 71c009d7ddf23..4e2e5193c9ba6 100755 --- a/docs/html/tools/debugging/debugging-memory.jd +++ b/docs/html/tools/debugging/debugging-memory.jd @@ -350,9 +350,9 @@ showing recent app allocations and stack traces in the Allocation Tracker.

Note: You will always see some allocations from {@code -DdmVmInternal} and else where that come from the allocation tracker itself.

+DdmVmInternal} and elsewhere that come from the allocation tracker itself.

-

Although it's not necessary (nor possible) to remove all allocations for your performance +

Although it's not necessary (nor possible) to remove all allocations from your performance critical code paths, the allocation tracker can help you identify important issues in your code. For instance, some apps might create a new {@link android.graphics.Paint} object on every draw. Moving that object into a global member is a simple fix that helps improve performance.