Automatically detect memory leaks in iOS UIView and UIViewController objects during development with instant alerts.
MLeaksFinder is an iOS development tool that automatically detects memory leaks in UIView and UIViewController objects during app development. It alerts developers immediately when leaks occur by displaying the leaked object's View-ViewController stack, helping identify and resolve memory management issues early.
iOS developers working with UIKit-based applications who need to proactively identify and fix memory leaks during the development phase.
Developers choose MLeaksFinder for its seamless, automatic integration that requires no manual code changes, providing real-time leak detection directly within the development environment without external tools.
Find memory leaks in your iOS app at develop time.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Installs via CocoaPods and activates automatically without any code changes or header imports, as specified in the Installation section, minimizing setup overhead.
Presents immediate alerts with the leaked object's View-ViewController stack when a leak is detected, helping developers catch issues early during development without external tools.
Allows developers to extend leak detection to other object types by overriding methods like `willDealloc` and using `MLCheck`, as demonstrated in the 'Find Leaks in Other Objects' section.
Provides a `willDealloc` method to mute alerts for intentionally non-deallocated objects like singletons, preventing false positives in edge cases.
Only detects leaks in UIView and UIViewController objects by default; extending to other types requires custom code, limiting out-of-the-box usefulness for complex apps with diverse object graphs.
FBRetainCycleDetector is removed due to licensing, so finding retain cycles requires manual pod installation and macro configuration, adding complexity and potential integration hurdles.
Key resources like the introduction and FAQ are primarily in Chinese, which may pose a barrier for developers who don't read the language, despite the English README.