facebook/fbretaincycledetector

iOS library to help detecting retain cycles in runtime.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 16th, 2026
Created on April 7th, 2016
Open Issues & Pull Requests: 43 (+0)
GitHub issues: Enabled
Number of forks: 601
Total Stargazers: 4,226 (+0)
Total Subscribers: 103 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 224.9 days
Mean response time: 268.1 days
90th percentile: 578.3 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,994 days
Stale 30+ days: 3
Stale 90+ days: 3

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

No issue events were indexed in the last 7 days.

Detailed Description

FBRetainCycleDetector is an iOS library that detects retain cycles at runtime.

The library addresses the problem of memory leaks caused by retain cycles in iOS applications. Retain cycles occur when objects hold strong references to each other, preventing them from being deallocated even when no longer needed. The tool works by analyzing object reference graphs at runtime to identify these problematic cycles before they cause memory issues in production.

Developers working on iOS projects should consider this library if memory management and leak prevention are priorities for their application. It is particularly suited for teams building long-running iOS applications where accumulated memory leaks can degrade performance over time. The library integrates into the development and testing workflow to catch retain cycles during development rather than discovering them through user-reported crashes or performance degradation in the field.

The project shows active maintenance with regular updates and bug fixes. The codebase demonstrates careful attention to edge cases and real-world iOS development scenarios. Development activity reflects a focus on stability and reliability rather than rapid feature expansion, with changes typically addressing specific issues encountered in production use.