OStack程序员社区-中国程序员成长平台

标题: ios - 如何修复 Objective-C 中的内存泄漏? [打印本页]

作者: 菜鸟教程小白    时间: 2022-12-12 15:42
标题: ios - 如何修复 Objective-C 中的内存泄漏?

我构建了一个从 HockeyApp 获取报告的简单应用程序。但是,当我使用内存泄漏工具运行应用程序时,它显示当我执行 getReport 操作时存在内存泄漏。我无法理解仪器中显示的所有信息。

这是导致内存泄漏的按钮操作方法:

- (IBAction)getReportsid)sender {

//initialize url that is going to be fetched.
NSURL *url = [NSURL URLWithString"https://rink.hockeyapp.net/api/2/apps/APP_ID/crash_reasons"];

//initialize a request from url
NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:url];
[request addValue:tokenReceived forHTTPHeaderField"X-HockeyAppToken"];

[request setHTTPMethod"GET"];
[request setValue"application/x-www-form-urlencoded" forHTTPHeaderField"Content-Type"];

//initialize a connection from request
NSURLConnection *connection = [[NSURLConnection alloc] initWithRequest:request delegate:self];
self.getReportConnection = connection;

}


- (void)connectionNSURLConnection *)connection didReceiveDataNSData*)data{

    if (connection==getReportConnection) {

     [self.receivedData appendData:data];

     NSLog(@"data is %@",data);

    NSString *responseString = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];

    NSError *e = nil;
    NSData *jsonData = [responseString dataUsingEncoding:NSUTF8StringEncoding];

    NSDictionary *JSON = [NSJSONSerialization JSONObjectWithData:jsonData options: NSJSONReadingMutableContainers error: &e];
    NSLog(@"login json is %@",JSON);
     NSLog(@"reason json is %@",JSON[@"reason"]);

    [JSON[@"crash_reasons"] enumerateObjectsUsingBlock:^(id obj, NSUInteger idx, BOOL *stop) {


        [reportArray addObjectbj[@"reason"]];
         NSLog(@"index = %lu, Object For title Key = %@", (unsigned long)idx, obj[@"reason"]);
    }];

    NSError *error = nil;
    NSArray *jsonArray = [NSJSONSerialization JSONObjectWithData:jsonData
                                                         options:kNilOptions error:&error];

    if (error != nil) {
        NSLog(@"Error parsing JSON.");
    }
    else {
        NSLog(@"Array: %@,array count is %d", jsonArray,jsonArray.count);
    }

   // [reportArray addObject:[jsonArray objectAtIndex:0]];

    if (JSON!=NULL) {
        UIAlertView *alert=[[UIAlertView alloc]initWithTitle"Reports succesfully retrieved" message"" delegate:self cancelButtonTitle"Ok" otherButtonTitles: nil];
        [alert show];
    }

       }
}

 // This method receives the error report in case of connection is not made to server.
 - (void)connectionNSURLConnection *)connection didFailWithErrorNSError *)error{

UIAlertView *errorAlert=[[UIAlertView alloc]initWithTitle"Wrong Login" message:nil delegate:self cancelButtonTitle"ok" otherButtonTitles: nil];
[errorAlert show];
NSLog(@"error is %@",error);
}

// This method is used to process the data after connection has made successfully.
- (void)connectionDidFinishLoadingNSURLConnection *)connection{

}

我发现内存泄漏发生在 didRecieveData 方法中出现警报 View 之前。

这里是内存泄漏工具显示内存泄漏的截图:

enter image description here

我不明白代码的哪一部分导致了内存泄漏。谁能告诉我如何使用泄漏工具识别导致内存泄漏的代码部分?

编辑:当我在模拟器上运行应用程序时,仪器没有显示任何内存泄漏:

截图如下: enter image description here

当我在设备上运行应用程序时,仪器再次显示内存泄漏: enter image description here

我查看了泄漏部分,发现 NSmutableArray 导致了泄漏: enter image description here enter image description here

我在我的代码中只使用了一个 NSMutableArray。我在 .h 文件中声明了它:

@property (nonatomic,strong) NSMutableArray *reportArray;

并在viewDidLoad中分配:

reportArray=[[NSMutableArray alloc]init];

并将其加载到 didRecieveData:

 [reportArray addObjectbj[@"reason"]];

堆栈跟踪快照:

enter image description here enter image description here enter image description here



Best Answer-推荐答案


试试这个:

reportArray = [[[NSMutableArray alloc] init] autorelease];

在您的 connectionDidFinishLoading:connection:didFailWithError: 方法中设置

reportArray = nil

最后在 Project > Build Phases > Compile Sources 添加 -fno-objc-arc 作为编译器标志此文件 (已编辑,抱歉)。然后再次点击 Product menu >Analyze (command + shift + B),查看是否还存在内存泄漏。

关于ios - 如何修复 Objective-C 中的内存泄漏?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/31208743/






欢迎光临 OStack程序员社区-中国程序员成长平台 (https://ostack.cn/) Powered by Discuz! X3.4