我也遇到了，用的系统样式自带的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:框架非常赞 : )

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 )

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

报错信息：

引入的库 FBRetainCycleDetector 报错： Pods/FBRetainCycleDetector/FBRetainCycleDetector/Layout/Classes/FBClassStrongLayout.mm:202:21: error: cannot initialize a parameter of type 'id _Nonnull' with an rvalue of type 'Class'

版本信息：

1.0.0

报错源码上下文：

NSArray<id<FBObjectReference>> *FBGetObjectStrongReferences(id obj,
                                                            NSMutableDictionary<Class, NSArray<id<FBObjectReference>> *> *layoutCache) {
  NSMutableArray<id<FBObjectReference>> *array = [NSMutableArray new];

  __unsafe_unretained Class previousClass = nil;
  __unsafe_unretained Class currentClass = object_getClass(obj);

  while (previousClass != currentClass) {
    NSArray<id<FBObjectReference>> *ivars;
    
    if (layoutCache && currentClass) {
      ivars = layoutCache[currentClass];
    }
    
    if (!ivars) {
      ivars = FBGetStrongReferencesForClass(currentClass);
      if (layoutCache && currentClass) {
        layoutCache[currentClass] = ivars; // 此处报错
      }
    }
    [array addObjectsFromArray:ivars];

    previousClass = currentClass;
    currentClass = class_getSuperclass(currentClass);
  }

  return [array copy];
}

现在 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

2017-09-26 18:24:10.158648+0800 BMOnlineManagement[14988:6444866] 控制器[BMSettingViewController]销毁了
2017-09-26 18:24:11.788183+0800 BMOnlineManagement[14988:6444866] Memory Leak: (
	BMSettingViewController,
	UIView
)
2017-09-26 18:24:11.788586+0800 BMOnlineManagement[14988:6444866] Possibly Memory Leak.
In case that UIView should not be dealloced, override -willDealloc in UIView by returning NO.
View-ViewController stack: (
    BMSettingViewController,
    UIView
)

https://github.com/Zepo/MLeaksFinder/commit/66b071fafab2bbf0f21bc88f434197fc84c6a56d

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

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]; }

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:^{}]; }

1. __strong id strongSelf = weakSelf;的意义是什么？
2. __strong id strongSelf = weakSelf;和__strong typeof(weakSelf) self = weakSelf;还不太一样，后者在GCD之后对weakSelf解除强引用，前者在GCD之前就不对weakSelf进行强引用了。

Whenever an alert comes up showing a memory leak in a view or viewController. post clicking on retain cycle button, it always shows the error of failing to find retain cycle.