Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Debugging and Profiling Apps

Sofia Palamarchuk edited this page Aug 16, 2021 · 19 revisions

Overview

(Needs Attention)

In addition, the following concepts need to be included:

  • Profiling GPU Rendering - quick visual representation of how much time it takes to render the frames of a UI window relative to the 16-ms-per-frame benchmark.
  • Visualizing Overdraw - Shows on the device where an app might be doing more rendering work than necessary. Helping you see where you might be able to reduce rendering overhead.
  • Heap Viewer - Identifying memory leaks
  • LeakCanary for finding memory leaks easily
  • Allocation Tracker - Finding the places in your code that may contribute to memory trashing.
  • Batterystats - Shows where and how processes are drawing current from the battery.
  • Batteryhistorian - Visualize system and application level events on a timeline. Guide to getting started

Optimizing Performance

Check out the following links regarding optimizing performance:

Memory Management

References

Finding these guides helpful?

We need help from the broader community to improve these guides, add new topics and keep the topics up-to-date. See our contribution guidelines here and our topic issues list for great ways to help out.

Check these same guides through our standalone viewer for a better browsing experience and an improved search. Follow us on twitter @codepath for access to more useful Android development resources.

Clone this wiki locally

AltStyle によって変換されたページ (->オリジナル) /