E-COM-NET

Question

I have a view containing a UIWebView which is loading a google map (so lots of javascript etc). The problem I have is that if the user hits the 'back' button on the nav bar before the web view has finished loading, it is not clear to me how to tidily tell the web view to stop loading and then release it, without getting messages sent to the deallocated instance. I'm also not sure that a web view likes its container view disappearing before it's done (but I've no choice if the user hits the back button before it's loaded).

In my viewWillDisappear handler I have this

map.delegate=nil;[self.map stopLoading];

this seems to handle most cases OK, as nil'ing the delegate stops it sending the didFailLoadWithError to my view controller. However if I release the web view in my view's dealloc method, sometimes (intermittently) I will still get a message sent to the deallocated instance, which seems to be related to the javascript running in the actual page, e.g.:

-[UIWebView webView:runJavaScriptAlertPanelWithMessage:initiatedByFrame:]: message sent to deallocated instance 0x4469ee0

If I simply don't release the webview, then I don't get these messages though I guess I'm then leaking the webview.

If I don't send the 'stopLoading' message, and simply release the webview within viewWillDisappear, then I see messages like this:

/SourceCache/WebCore/WebCore-351.9.42/wak/WKWindow.c:250WKWindowIsSuspendedWindow: NULL window.

Possibly related, I sometimes (again totally intermittent) get an ugly heisenbug where clicking the back button on some other view's navbar will pop the title, but not the view. In other words I get left with the title of view n on the stack, but the view showing is still view n+1 (the result is you're trapped on this screen and cannot get back to the root view - you can go the other direction, i.e. push more views and pop back to the view that didn't pop corrrectly, just not to the root view. The only way out is to quit the app). At other times the same sequence of pushes and pops on the same views works fine.

This particular one is driving me nuts. I think it may be related to the view disappearing before the web view is loaded, i.e. in this case I suspect it may scribble on memory and confuse the view stack. Or, this could be completely unrelated and a bug somewhere else (i've never been able to reproduce it in debug build mode, it only happens with release build settings when I can't watch it with gdb :-). From my debug runs, I don't think I'm over-releasing anything. And I only seem to be able to trigger it if at some point I have hit the view that has the web view, and it doesn't happen immediately after that.

If I were you, I'd file a bug with Apple. The web view should not be receiving any messages after it gets deallocated -- it ought to terminate JS processing and URL loading when it's dealloc'ed. I've seen the nav item issue occasionally, but only after I installed iPhone OS 3.0 beta. Maybe that's an OS bug, too?
yes that's what I thought (dealloc should clean up). The apple docs aren't generally very clear on the contract with the objects they provide. I've never seen the nav thing before and it happens regularly enough in my program that I think it must be something I'm doing - hopefully related to this webview thing if I manage to fix it.
try setting the webView as associated object instead of ivar/property

rpetrich · Accepted Answer · 2011-03-12 07:25:54Z

up vote 41 down vote accepted

+125

A variation on this should fix both the leaking and zombie issues:

-(void)loadRequest:(NSURLRequest*)request {[self retain];if([webView isLoading])[webView stopLoading];[webView loadRequest:request];[self release];}-(void)webViewDidStartLoad:(UIWebView*)webView {[self retain];}-(void)webViewDidFinishLoad:(UIWebView*)webView {[self release];}-(void)webView:(UIWebView*)webView didFailLoadWithError:(NSError*)error {[self release];}-(void)viewWillDisappear {if([webView isLoading])[webView stopLoading];}-(void)dealloc {[webView setDelegate:nil];[webView release];[super dealloc];}

edited Mar 12 '11 at 7:25

answered May 5 '09 at 23:09

rpetrich
23.2k 4 41 71

yes good answer, i was thinking of trying something like this. your answer has a few things i didn't think of though, so i'll try it and if it works I will accept this one. Unfortunately the bounty will expire before i get time to try this - but what I will do is reopen the bounty and accept the answer in that case (just to remind myself, it was 250 bounty). – frankodwyer May 8 '09 at 12:24

I wouldn't worry about the bounty too much. It's just a number (besides, half is awarded to the top answer anyway ;) – rpetrich May 8 '09 at 23:54

finally got around to trying this - looking pretty good so far. No funny messages and it even seems to have cured the heisenbug - it was pretty intermittent though so I won't cheer yet til I have tested some more. – frankodwyer Jun 12 '09 at 21:03

@rpetrich: I know it's past 2nd anniversary of your answer, but why the fix is using retain/release onself? Wouldn't that cause problems for didReceiveMemoryNotification or forced call ofviewDidUnload? Could you please put some more light on why retain/release is used for a view controller which (I assume) has UIWebView outlet as property? – matm Jun 8 '11 at 9:12

@rpetrich: I think calling [self release] for [webView isLoading] == YES in viewDidUnloadshould balance retain count if e.g. webView has a long timeout, connection is slow and view is forced to unload. Am I correct? – matm Jun 8 '11 at 9:19

show 6 more comments

Armaggi · Answer 2 · 2009-06-30 16:29:17Z

up vote 1 down vote

The UINavigationController bug you're describing in the second part of your post might be related to your handling of memory warnings. I've experienced this phenomenon and I"ve been able to reproduce it on view n in the stack by simulating a memory warning while viewing view (n+1) in the stack.

UIWebView is a memory eater, so getting memory warnings wouldn't be surprising when it's used as part of a view hierarchy.

answered Jun 30 '09 at 16:29

Armaggi

That's interesting, thanks. I will read up on what I'm meant to do in response to a memory warning (right now I don't handle it at all). I have not actually seen this issue since I moved to 3.0 and dumped the webview in favor of mapkit, and generally tightened up on other areas of memory handling. – frankodwyer Jun 30 '09 at 16:50

add comment (requires 50 reputation)

Can Berk Güder · Answer 3 · 2009-04-26 02:35:57Z

up vote 0 down vote

A simple release message in dealloc ought to be enough.

Your second problem sounds like a prematurely deallocated view, but I can't say much without seeing some code.

answered Apr 26 '09 at 2:35

Can Berk Güder
32.8k 11 76 109

yes a simple release in dealloc is what I had, and this is what results in the message getting sent to the deallocated instance. The webview is declared with @property (nonatomic,retain) if that makes a difference. Also, I have NSZombie checking on and otherwise I don't see any messages going to deallocated views - also as I say I can't reproduce this at all in Debug mode, it only happens in release mode. – frankodwyer Apr 26 '09 at 9:36

add comment (requires 50 reputation)

dieselmcfadden · Answer 4 · 2009-05-03 07:47:20Z

There's a few ways to handle it, but this should work. You want the didFailLoadWithError message, it's what tells you it's stopped.

Set a flag isLeaving=YES; Send the Webview a stopLoading.

In didFailLoadWithError:, check for the error you get when the webview stops:

if ((thiserror.code == NSURLErrorCancelled) && (isLeaving==YES)) {

[otherClass performSelector:@selector(shootWebview) withObject:nil withDelay:0]

}

release the webView in shootWebview:

variations: if you want to be cavalier about it, you can do the performSelector:withObject:withDelay: with a delay of [fillintheblank], call it 10-30 seconds without the check and you'll almost certainly get away with it, though I don't recommend it.

You can have the didFailLoadWithError set a flag and clean it up somewhere else.

or my favorite, maybe you don't need to dealloc it all when you leave. Won't you ever display that view container again? why not keep it around reuse it?

Your debug being different from release issue, you might want to check your configuration to make sure that it's exactly the same. Bounty was on the reproducible part of the question, right? ;-).

-- Oh wait a second, you might be taking a whole View container down with the WebView. You can do a variation on the above and wait to release the whole container in shootWebView.

my problem is that once I get the viewWillDisappear message, my view controller is going away and will shortly be dealloced (along with everything it contains, i.e. the webview). I don't see any way to prevent the view controller being dealloced (without leaking it) as it's not me that does that. Hence any delegate messages will (sometimes) wind up going to the dealloced instance of my controller.
This sounds wonky even as I type it, but I suppose you could [self retain] before your webview loading calls and balance by [self release] in the didfinishload and didfailloads to make sure everything sticks around until the WebViews complete properly.
yes I was thinking along those lines myself, and like you I thought it was a bit wonky - don't see why it shouldn't work tho. Will try this, along the lines of rpetrich's answer.

abuharsky · Answer 5 · 2009-09-08 07:33:18Z

Possibly related, I sometimes (again totally intermittent) get an ugly heisenbug where clicking the back button on some other view's navbar will pop the title, but not the view. In other words I get left with the title of view n on the stack, but the view showing is still view n+1 (the result is you're trapped on this screen and cannot get back to the root view - you can go the other direction, i.e. push more views and pop back to the view that didn't pop corrrectly, just not to the root view. The only way out is to quit the app). At other times the same sequence of pushes and pops on the same views works fine.

I have the same problem, when I'm use navigation controller with view controllers in stack > 2 and current view controller index > 2, if an memoryWarning occurs in this momens, it raises the same problems.

There is inly 1 solution, which I found after many experiments with overriding pop and push methods in NavigationController, with the stack of view controllers, with views and superviews for stacked ViewControllers, etc.

#import <UIKit/UIKit.h>#import <Foundation/Foundation.h>@interfaceFixedNavigationController:UINavigationController<UINavigationControllerDelegate>{}@end

#import "FixedNavigationController.h"static BOOL bugDetected = NO;@implementationFixedNavigationController-(void)viewDidLoad{[self setDelegate:self];}-(void)didReceiveMemoryWarning{// FIX navigationController & memory warning bugif([self.viewControllers count]>2) bugDetected = YES;}-(void)navigationController:(UINavigationController*)navigationController didShowViewController:(UIViewController*)viewController animated:(BOOL)animated {// FIX navigationController & memory warning bugif(bugDetected){ bugDetected = NO;if(viewController ==[self.viewControllers objectAtIndex:1]){[self popToRootViewControllerAnimated:NO]; self.viewControllers =[self.viewControllers arrayByAddingObject:viewController];}}}@end

It works fine for 3 view controllers in stack.

TimM · Answer 6 · 2009-08-17 14:34:18Z

I had a similar problem to this using a UIWebView in OS3 - this description was a good starting point, however I found than simply nil'ing out the web view delegate before releasing the webView solved my problem.

Reading the sample code (the accepted answer - above) - it seems like a lot of overkill. E.g. [webView release] and webView = nil lines do exactly the same thing given the way the author describes the variable is declared (so you don't need both). I'm also not fully convinced by all the retain and release lines either - but I guess your mileage will vary.

How to safely shut down a loading UIWebView in viewWillDisappear?

6 Answers

你可能感兴趣的:(UIWebView)