Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 634caa4e authored by Dan Dascalescu's avatar Dan Dascalescu
Browse files

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
parent d277d908

docs/html/tools/debugging/debugging-memory.jd

+2 −2
Original line number Diff line number Diff line
@@ -352,7 +352,7 @@ showing recent app allocations and stack traces in the Allocation Tracker.</p> 
<p class="note"><strong>Note:</strong> You will always see some allocations from {@code

DdmVmInternal} and elsewhere that come from the allocation tracker itself.</p>



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

<p>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.</p>