krzysztofzablocki/LifetimeTracker

Find retain cycles / memory leaks sooner.

View on GitHub ↗Jump to charts ↓

krzysztofzablocki/LifetimeTracker has 3k+ stars and 150+ forks on GitHub, is written in Swift, and was last pushed on Mar 5, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on July 31st, 2017
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 154
Total Stargazers: 3,313 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 171.2 days
90th percentile: 795.9 days
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 519 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

LifetimeTracker is a memory leak detection tool for iOS that surfaces retain cycles during development rather than requiring manual investigation with Instruments or the Memory Graph Debugger.

The tool addresses the problem that developers often forget to check for memory issues after completing feature implementation, and when they do use standard debugging tools sporadically, the investigation becomes time-consuming. LifetimeTracker works by tracking the lifetime of objects you designate as key actors in your application, such as ViewModels or Controllers. Unlike tools that rely on Objective-C runtime introspection, it uses explicit tracking that works equally well with pure Swift classes and Objective-C code. When tracked objects exceed a configured maximum count, the tool immediately surfaces a notification on screen, making issues visible as they occur.

Developers should adopt this tool if they want continuous, passive memory leak detection integrated into their development workflow without the overhead of manual debugging sessions. It suits projects where you can identify and annotate key actors that should have bounded lifetimes. The tool offers two visual styles: an overlay bar that displays detailed issue lists directly on screen, or a circular indicator that shows issue counts and opens details in a modal. It integrates with Danger for pull request automation, allowing teams to enforce that developers verify no retain cycles were introduced and that tracking calls were not forgotten.

Development activity shows consistent maintenance with regular updates addressing issues and adding refinements. The project demonstrates responsiveness to user-reported problems and incorporates community feedback into improvements. Work includes both core functionality enhancements and developer experience features like the Danger integration and configuration options for controlling dashboard visibility.