FBRetainCycleDetector alternatives and similar libraries
Based on the "Code Quality" category.
Alternatively, view FBRetainCycleDetector alternatives based on common mentions on social networks and blogs.
-
CleanArchitectureRxSwift
Example of Clean Architecture of iOS app using RxSwift. -
KZBootstrap
iOS project bootstrap aimed at high quality coding. -
HeapInspector-for-iOS
Find memory issues & leaks in your iOS app without instruments -
Tailor
Cross-platform static analyzer for Swift that helps you to write cleaner code and avoid bugs. -
IBAnalyzer
Find common xib and storyboard-related problems without running your app or writing unit tests. -
dotenv-linter
⚡️Lightning-fast linter for .env files. Written in Rust 🦀 -
SwiftCop
SwiftCop is a validation library fully written in Swift and inspired by the clarity of Ruby On Rails Active Record validations. -
Viperit
Viper Framework for iOS. Develop an app following VIPER architecture in an easy way. Written and tested in Swift. -
Warnings-xcconfig
An xcconfig (Xcode configuration) file for easily turning on a boatload of warnings in your project or its targets. -
Clue
Flexible bug report framework for iOS with screencast, networking, interactions and view structure. -
Marshroute
Marshroute is an iOS Library for making your Routers simple but extremely powerful. -
PSTModernizer
Makes it easier to support older versions of iOS by fixing things and adding missing methods. -
Trackable
Trackable is a simple analytics integration helper library. It’s especially designed for easy and comfortable integration with existing projects. -
KZAsserts
Set of custom assertions that automatically generate NSError's, allow for both Assertions in Debug and Error handling in Release builds, with beautiful DSL. -
WeakableSelf
A Swift micro-framework to encapsulate [weak self] and guard statements within closures. -
UIBaseKit
This helps make the view's configuration code, hierarchy code, and constraint code neat. -
SwiftLinter
Share lint rules between projects and lint changed files with SwiftLint. -
Bugsee
In-app bug and crash reporting with video, logs, network traffic and traces.
Get performance insights in less than 4 minutes
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of FBRetainCycleDetector or a related project?
README
FBRetainCycleDetector
An iOS library that finds retain cycles using runtime analysis.
About
Retain cycles are one of the most common ways of creating memory leaks. It's incredibly easy to create a retain cycle, and tends to be hard to spot it. The goal of FBRetainCycleDetector is to help find retain cycles at runtime. The features of this project were influenced by Circle.
Installation
Carthage
To your Cartfile add:
github "facebook/FBRetainCycleDetector"
FBRetainCycleDetector
is built out from non-debug builds, so when you want to test it, use
carthage update --configuration Debug
CocoaPods
To your podspec add:
pod 'FBRetainCycleDetector'
You'll be able to use FBRetainCycleDetector
fully only in Debug
builds. This is controlled by compilation flag that can be provided to the build to make it work in other configurations.
Example usage
Let's quickly dive in
#import <FBRetainCycleDetector/FBRetainCycleDetector.h>
FBRetainCycleDetector *detector = [FBRetainCycleDetector new];
[detector addCandidate:myObject];
NSSet *retainCycles = [detector findRetainCycles];
NSLog(@"%@", retainCycles);
- (NSSet<NSArray<FBObjectiveCGraphElement *> *> *)findRetainCycles
will return a set of arrays of wrapped objects. It's pretty hard to look at at first, but let's go through it. Every array in this set will represent one retain cycle. Every element in this array is a wrapper around one object in this retain cycle. Check FBObjectiveCGraphElement.
Example output could look like this:
{(
(
"-> MyObject ",
"-> _someObject -> __NSArrayI "
)
)}
MyObject
through someObject
property retained NSArray
that it was a part of.
FBRetainCycleDetector will look for cycles that are no longer than 10 objects. We can make it bigger (although it's going to be slower!).
FBRetainCycleDetector *detector = [FBRetainCycleDetector new];
[detector addCandidate:myObject];
NSSet *retainCycles = [detector findRetainCyclesWithMaxCycleLength:100];
Filters
There could also be retain cycles that we would like to omit. It's because not every retain cycle is a leak, and we might want to filter them out. To do so we need to specify filters:
NSMutableArray *filters = @[
FBFilterBlockWithObjectIvarRelation([UIView class], @"_subviewCache"),
];
// Configuration object can describe filters as well as some options
FBObjectGraphConfiguration *configuration =
[[FBObjectGraphConfiguration alloc] initWithFilterBlocks:filters
shouldInspectTimers:YES];
FBRetainCycleDetector *detector = [[FBRetainCycleDetector alloc] initWithConfiguration:configuration];
[detector addCandidate:myObject];
NSSet *retainCycles = [detector findRetainCycles];
Every filter is a block that having two FBObjectiveCGraphElement
objects can say, if their relation is valid.
Check [FBStandardGraphEdgeFilters](FBRetainCycleDetector/Filtering/FBStandardGraphEdgeFilters.h) to learn more about how to use filters.
NSTimer
NSTimer can be troublesome as it will retain it's target. Oftentimes it means a retain cycle. FBRetainCycleDetector
can detect those,
but if you want to skip them, you can specify that in the configuration you are passing to FBRetainCycleDetector
.
FBObjectGraphConfiguration *configuration =
[[FBObjectGraphConfiguration alloc] initWithFilterBlocks:someFilters
shouldInspectTimers:NO];
FBRetainCycleDetector *detector = [[FBRetainCycleDetector alloc] initWithConfiguration:configuration];
Associations
Objective-C let's us set associated objects for every object using objc_setAssociatedObject.
These associated objects can lead to retain cycles if we use retaining policies, like OBJC_ASSOCIATION_RETAIN_NONATOMIC
. FBRetainCycleDetector can catch these kinds of cycles, but to do so we need to set it up. Early in the application's lifetime, preferably in main.m
we can add this:
#import <FBRetainCycleDetector/FBAssociationManager.h>
int main(int argc, char * argv[]) {
@autoreleasepool {
[FBAssociationManager hook];
return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
}
}
In the code above [FBAssociationManager hook]
will use fishhook to interpose functions objc_setAssociatedObject
and objc_resetAssociatedObjects
to track associations before they are made.
Getting Candidates
If you want to profile your app, you might want to have an abstraction over how to get candidates for FBRetainCycleDetector
. While you can simply track it your own, you can also use FBAllocationTracker. It's a small tool we created that can help you track the objects. It offers simple API that you can query for example for all instances of given class, or all class names currently tracked, etc.
FBAllocationTracker
and FBRetainCycleDetector
can work nicely together. We have created a small example and drop-in project called FBMemoryProfiler that leverages both these projects. It offers you very basic UI that you can use to track all allocations and force retain cycle detection from UI.
Contributing
See the [CONTRIBUTING](CONTRIBUTING.md) file for how to help out.
License
[FBRetainCycleDetector
is BSD-licensed](LICENSE).
*Note that all licence references and agreements mentioned in the FBRetainCycleDetector README section above
are relevant to that project's source code only.