Skip to content
CAI
Produce a survey ↗Verify a survey

square/leakcanary

This system is a memory leak detection and analysis toolkit for Android and JVM applications. It provides object tracking to identify unreachable objects, heap dump capture, and automated leak analysis to report retained memory. The platform includes a command-line interface for processing heap dumps, a Gradle plugin for deobfuscation, and comprehensive test utilities for verifying leak detection in both unit and instrumentation tests.

53.6

Adequate · 5 August 2026

35k

lines of production code

Kotlin

primary language

1

bus factor · 174 authors in all

4

measurements over time

CAI band scale
CAI trend line

How it got here

2015–2023 · Android platform integration and analysis engine

The project evolved from a generic memory leak detection library into a comprehensive Android-specific tool, introducing automatic lifecycle tracking for Activities, Fragments, and ViewModels. The core analysis engine was significantly expanded to handle Android heap dumps, extract device metadata, and filter known framework leaks. Additionally, a full-featured Android application and CLI were built to visualize results, while the build system was modernized to Kotlin DSL.

34 changes

2024 · In-process test support and heap dump management

This period focused on enabling in-process heap dump analysis for both JVM and Android UI Automator tests, allowing memory leak detection directly within automated test scenarios. The work introduced new public APIs for managing heap dump storage and lifecycle, alongside comprehensive test coverage to validate object growth detection across various environments.

13 changes

CAI lens gauges

Survey your own repository

square/leakcanary was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.

Survey a repository

About this page

  • The description of this project is derived from its own commit history, not from its README.
  • The score is its highest published measurement, taken on 5 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit bcf276e04d — the exact code this score is about.
  • Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.
CAI link cards