我自定义导航栏返回按钮自己写pop 事件， 来回的跳转几次就报错误

最通过莫过于，知道泄漏问题，但是找不到。。。

通过pod管理代码 pod 'MLeaksFinder', :configurations => ['Debug']，没有生效，load方法都没有执行。如果是把文件夹拖入项目的话就没问题，请问可能是因为什么原因导致的？谢谢！

请问，崩在这个方法是什么原因导致的？

Retain Cycle: (
"-> mockParent -> CartTableViewCell ",
"-> __associated_object -> __NSDictionaryM ",
"-> _AXTableViewCellInternal "
)
出现 这个 这个貌似是系统UIKit下边的一个类。。大神 我这是怎么了 求指教

添加断点，看到已经执行了MainViewController的dealloc方法。 但是提示UITableview没有被释放，这个UITableview是通过Xib添加的。

In case that UITableView should not be dealloced, override -willDealloc in UITableView by returning NO.
View-ViewController stack: (
MainViewController,
UIView,
UIView,
UITableView
)

闪退信息如下：
*** Assertion failure in -[CalendarVC assertNotDealloc], ..../Vendor/MLeaksFinder/NSObject+MemoryLeak.m:43
libc++abi.dylib: terminate_handler unexpectedly threw an exception

调用popViewControllerAnimated不提示内存泄露。
没有检测到循环引用。
利用 instruments 的 leaks 也没有发现内存泄露。
但是我用系统 navigation 的侧滑返回以及点返回按钮都提示内存泄露 help...

Hi,

It's a wonderful util to me to find my memory leaks in my APP, it's really useful!

I'd like to suggest add a variable/Macro to switch leaks finder on or off, you know in release package, it's needless to throw a exception to exit the app due to memory leak, but during debug.

Thanks a lot!

roby

#ifdef MEMORY_LEAKS_FINDER_RETAIN_CYCLE_ENABLED
#define _INTERNAL_MLF_RC_ENABLED MEMORY_LEAKS_FINDER_RETAIN_CYCLE_ENABLED
#elif COCOAPODS
#define _INTERNAL_MLF_RC_ENABLED COCOAPODS
#endif
一般项目的cocoa pods这个宏一直都是1 那么上线后如果发现循环引用也要弹出alertView了啊

支持swift么 有没有demo

Since we may override a class !

@Zepo 你好，烦请看下
代码比较简单，一个TableviewCell，里边只有一个label，特意在dealloc中加了NSLog输出：
以下是TableviewCell的代码：

以下是console的输出，明显看到dealloc有执行NSLog()

Memory Leak: (
UIImagePickerController,
PLUICameraViewController,
PLImagePickerCameraView
)

Possibly Memory Leak.
In case that PLImagePickerCameraView should not be dealloced, override -willDealloc in PLImagePickerCameraView by returning NO.
View-ViewController stack: (
UIImagePickerController,
PLUICameraViewController,
PLImagePickerCameraView
)

在cocoapods环境下想运行非cocooapods的代码，我把NSObject+MemoryLeak.h文件的宏注释掉了，还是不运行，请问判断是否是cocoapods环境的宏是怎么定义的？

现在同一个地方内存泄露，弹出好几次提示框！用的pod导入！

In case that UIWebOverflowScrollView should not be dealloced, override -willDealloc in UIWebOverflowScrollView by returning NO.
View-ViewController stack: (
BFSMatchJumpViewController,
UIView,
UIView,
WMScrollView,
UIView,
UIWebView,
"_UIWebViewScrollView",
UIWebBrowserView,
UIWebOverflowScrollView
)

Hi:
I just pod MLeaksFinder, when setting Xcode Release mode MLeaksFinder also work.

手动添加整个工程之后，在 UIViewController+MemoryLeak.m 的 + (void)load 方法里加断点，断点没有进入。

如题, 因为有些页面是用的那两个方法添加和移出的, 希望可以拓展这个库的能力

ViewController A present ViewController B and B implementation this method, B's root view always leak
- (void)touchesBegan:(NSSet<UITouch *> *)touches withEvent:(UIEvent *)event { [self cancelAction:nil]; [self dismissViewControllerAnimated:animated completion:nil]; }

这个我们自己无法控制吧？
检测的原理是啥呢？

controller中若有网络请求的话，网络请求的block回调中一般都是直接引用self变量的，这样就导致controller除非在网络请求的block落地之前是不会被析构的，如果在这之前页面被pop掉，很容易出现误报

项目中存在大量native与UIWebView交互的情况，在vc, webview 都dealloc的情况下还是会中断言，View-ViewController stack: [
TSearchViewController,
UIView,
TWebView,
_UIWebViewScrollView,
UIWebBrowserView
]'

在一个ViewController中cellForRow的代理方法里创建一个UISwitch并作为cell的accessoryView,代码如下：
if (indexPath.row == 3) {
UISwitch *s = [[UISwitch alloc] init];
NSUserDefaults *userD = [NSUserDefaults standardUserDefaults];
s.on = [[userD objectForKey:kWiFiKey] boolValue];
[s addTarget:self action:@selector(promptOn:) forControlEvents:UIControlEventValueChanged];
cell.accessoryView = s;
}

当退出当前controller时, 提示内存泄漏，提示如下：
In case that UISwitch should not be dealloced, override -willDealloc in UISwitch by returning NO.
View-ViewController stack: (
LilySettingViewController,
UIView,
UIView,
UITableView,
UITableViewWrapperView,
UITableViewCell,
UISwitch
)

用Instruments工具分析无内存泄漏，并且当前controller的dealloc方法已执行。

打包release环境的ipa包时, ipa包里含有FBRetainCycleDetector的文件, cocoaPods里这样写的 pod 'MLeaksFinder', :configurations => ['Debug’], 这样打release包时没有MLeaksFinder, 但有FBRetainCycleDetector. MLeaksFinder.podspec里是这样写的, s.dependency 'FBRetainCycleDetector’, 是否要做处理以便区分编译环境?

log as follows:

2016-08-20 15:45:53.723 ERPProject[11890:196011] Memory Leak: (
    MLBReportFormsCommonViewController,
    UIView,
    MLBReportFormsFilteringView,
    UIScrollView,
    UIKeyboardCandidateInlineFloatingView
)
2016-08-20 15:45:53.723 ERPProject[11890:196011] Possibly Memory Leak.
In case that UIKeyboardCandidateInlineFloatingView should not be dealloced, override -willDealloc in UIKeyboardCandidateInlineFloatingView by returning NO.
View-ViewController stack: (
    MLBReportFormsCommonViewController,
    UIView,
    MLBReportFormsFilteringView,
    UIScrollView,
    UIKeyboardCandidateInlineFloatingView
)

在button 的点击事件或者UITableview 的点击Cell的事件中调用self.navigationController popViewControllerAnimated:YES 时就报没有释放

pragma mark -

pragma mark -UIImagePickerController

• (void)jumpToCameraOrPhotoLibraryWithType:(UIImagePickerControllerSourceType)type{
  UIImagePickerController *imagePickerController = [[UIImagePickerController alloc] init];
  imagePickerController.delegate = self;
  imagePickerController.allowsEditing = YES;
  imagePickerController.sourceType = type;
  [self presentViewController:imagePickerController animated:YES completion:^{}];
  }

// callback

• (void)imagePickerController:(UIImagePickerController *)picker didFinishPickingMediaWithInfo:(NSDictionary *)info
  {
  UIImage *image = [info objectForKey:UIImagePickerControllerEditedImage];
  self.imagUAvrtar.image = image;
  self.img2upload= image;
  [picker dismissViewControllerAnimated:YES completion:^{}];
  }
• (void)imagePickerControllerDidCancel:(UIImagePickerController *)picker{
  [self dismissViewControllerAnimated:YES completion:^{}];
  }

应该定义另外一个flag，例如MLENABLE，这样在debug下用户依然可以选择关闭MLeaksFinder

我也遇到了，用的系统样式自带的cell，在返回cell的方法如下：

• (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
  UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:kCellId forIndexPath:indexPath];
  VankeShopModel *shop = self.results[indexPath.row];
  cell.textLabel.text = [NSString stringWithFormat:@"%@【%@】", shop.name, shop.code];
  return cell;
  }

MLeakFinder提示：
Possibly Memory Leak.
In case that UITableViewCellContentView should not be dealloced, override -willDealloc in UITableViewCellContentView by returning NO.
View-ViewController stack: (
ChooseShopViewController,
UIView,
UITableView,
UITableViewWrapperView,
UITableViewCell,
UITableViewCellContentView
)

实在找不到哪里有内存泄露，希望对你完善框架有帮助。
PS:框架非常赞 : )

在pushed页面里添加按钮，按钮事件为执行pop。回到上一个页面后，如果没有屏幕interaction则报uibutton被持有，但controller被正确释放。此处应该是苹果的bug，但MLeaksFinder中可能还未添加处理。（SB和代码添加的button都有这个问题。由此推向所有UIControl相关的子类都有该问题，类似UIGesture已验证，但popGesture没问题）
另外，MLeaksFinder目前还未支持gitSpecs的搜索查询，引用pod成问题。

改成alert样式，其它代码没有任何变动，就没有泄露了。
我用的OC

在实际项目中，用了MLeaksFinder，但在SB中发现了一个问题。例如：在页面A跳转到页面B。页面B中有一个按钮，点击按钮是返回到页面A，如果直接手势返回，不会有什么问题。如果是点击页面B中的按钮返回，就会断言说按钮没有释放掉。不知道什么问题，求解答，写了个demo： https://github.com/vjieshao/MLeaksFinderTest 谢谢！

What is the meaning of this kind of circumstance is a circular reference, or no circular references

现在 pod 上的版本是0.1的.

使用01的版本的时候,发现了个 bug.
在 vc释放的时候,去调用 self.view 导致调用 [UIViewController loadViewIfRequired]

即为由 frame5->frame4->frame3的过程.

_cmd="doFetchDataWithParms:requestComplete:", parms=3 key/value pairs, complete=0x000000012e2e2230) + 96 at MeCollectController.m:21, queue = 'com.apple.main-thread', stop reason = breakpoint 4.1
  * frame #0: 0x00000001001785dc`-[MeCollectController doFetchDataWithParms:requestComplete:](self=0x000000012e6928b0, _cmd="doFetchDataWithParms:requestComplete:", parms=3 key/value pairs, complete=0x000000012e2e2230) + 96 at MeCollectController.m:21
    frame #1: 0x0000000100178a5c`-[MeCollectController fetchData](self=0x000000012e6928b0, _cmd="fetchData") + 252 at MeCollectController.m:45
    frame #2: 0x0000000100178570`-[MeCollectController viewDidLoad](self=0x000000012e6928b0, _cmd="viewDidLoad") + 256 at MeCollectController.m:17
    frame #3: 0x000000018680cc40 UIKit`-[UIViewController loadViewIfRequired] + 996
    frame #4: 0x000000018680c844 UIKit`-[UIViewController view] + 28
    frame #5: 0x00000001014653b0 MLeaksFinder`-[UIViewController(self=0x000000012e6928b0, _cmd="willDealloc") willDealloc] + 892 at UIViewController+MemoryLeak.m:75
    frame #6: 0x0000000101465244 MLeaksFinder`-[UIViewController(self=0x000000012e690ae0, _cmd="willDealloc") willDealloc] + 528 at UIViewController+MemoryLeak.m:65
    frame #7: 0x0000000101464de4 MLeaksFinder`-[UIViewController(self=0x000000012e690ae0, _cmd="viewDidDisappear:", animated=YES) swizzled_viewDidDisappear:] + 156 at UIViewController+MemoryLeak.m:32
    frame #8: 0x0000000192e2d394 UIKit`-[UIViewControllerAccessibility viewDidDisappear:] + 52
    frame #9: 0x00000001002d6ad0`-[UIViewController(self=0x000000012e690ae0, _cmd=<unavailable>, animated=<unavailable>) btg_swizzleViewDidDisappear:] + 28 at UIViewController+BTGMethodSwizzler.m:69
    frame #10: 0x0000000186825314 UIKit`-[UIViewController _setViewAppearState:isAnimating:] + 532
    frame #11: 0x000000018689d0cc UIKit`-[UIViewController __viewDidDisappear:] + 144

查看源码后发现使用 pod 上的 v0.1版本的缘故:

https://git.io/vK1M1

还请更新 pod 到0.2版本

3Q

[self.closestViewController.navigationController pushViewController:detailVC animated:YES];

then in detailVC:

SigninViewController *signinVC = [[SigninViewController alloc] init];
signinVC.delegate = self;
UINavigationController *nav = [[UINavigationController alloc] initWithRootViewController:signinVC];
[self presentViewController:nav animated:YES completion:nil];

If I call dismiss in signInVC:

[self dismissViewControllerAnimated:YES completion:nil];

modal viewcontroller closed and will report memory leak:

Zepo@66b071f

您好，不知道在哪里请教问题比较合适。所以还借此请教下，这个commit的修改里，为什么采用对象比较就会crash。而采用对象的地址比较就没问题呢？

i tested to make the keywindow's rootViewController be in a retain cycle, then assign to another viewcontroller, the old viewcontroller hasn't dealloced but MLeaksFinder detects nothing.

It seems that UISwitch can not be released (tested on iOS 10) in a right way. Should it be in the whitelist?