Skip to main content

How to download a large file with the iPhone SDK and avoid memory usage issues?



I'm using the NSURLConnection class to download a large file in my iPhone application, but it crashes every so often because it's using too much memory. I'm doing the usual NSURLConnection usage, to append the received data to a NSMutableData object.







- (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data {

[self.fileData appendData:data];

}







Then after I finish downloading the whole file, I save it to a local temporary file, and read it as a mapped file like this:







- (void)connectionDidFinishLoading:(NSURLConnection *)connection {

// save the downloaded data into a temporary file

NSString *tempPath = NSTemporaryDirectory();

NSString *tempFile = [tempPath stringByAppendingPathComponent:@"temp.pdf"];

[self.fileData writeToFile:tempFile atomically:YES];

NSData *mappedData = [NSData dataWithContentsOfMappedFile:tempFile];



NSURL *baseURL = [NSURL URLWithString:@"http://mydomain.com"];

[webView loadData:mappedData MIMEType:@"application/pdf" textEncodingName:@"UTF-8" baseURL:baseURL];

}







What can I improve here to avoid these memory usage problems?



Source: Tips4all

Comments

  1. If it's that large, why not write it to the file as it comes in, rather than keeping it in an NSData object?

    ReplyDelete
  2. - (void)connection:(NSURLConnection *)connection didReceiveResponse:(NSURLResponse*)response {

    filename = [[NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0] stringByAppendingPathComponent:save_name]; // filename is in .h file

    [[NSFileManager defaultManager] createFileAtPath:filename contents:nil attributes:nil];
    file =
    [[NSFileHandle fileHandleForUpdatingAtPath:filename] retain];// file is in .h

    if (file) {

    [file seekToEndOfFile];
    }
    }

    - (void)connection:(NSURLConnection *)connection didReceiveData:(NSD
    ata *)data {

    if (file) {

    [file seekToEndOfFile];

    } [file writeData:data];

    }

    - (void)connectionDidFinishLoading:(NSURLConnection*)connection {

    [file closeFile];

    }

    ReplyDelete
  3. i'm using

    - (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data
    {
    filename = [[NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0] stringByAppendingPathComponent:save_name];
    NSFileHandle *file1 = [NSFileHandle fileHandleForUpdatingAtPath: filename];
    [file1 writeData: data];
    [file1 closeFile];
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex