Re: knowing when WebView is done
Re: knowing when WebView is done
- Subject: Re: knowing when WebView is done
- From: Timothy Ritchey <email@hidden>
- Date: Sat, 07 Jun 2008 09:26:52 -0400
On Jun 7, 2008, at 1:32 AM, Adam R. Maxwell wrote:
Never. Since the frameworks retain/(auto)release stuff all the time
behind your back, logging -retainCount is worse than useless, in my
opinion.
Very good point. It looks like he call to setMainFrameURL is what
bumps up the retain count.
From a quick check with Instruments, it looks like internal WebKit
stuff is retaining the view for callbacks even after it's done
loading, then releasing it on a later pass through the runloop. I
wouldn't worry about it unless you're actually leaking the object.
From what I can tell by watching several instrument runs, it seems
like WebKit is internally caching stuff. If I go to cnn.com, I see a
major memory bump, but I can go to it again and again and not see any
increase, but when I go to a new website, say digg.com, I see another
memory bump again. Even if I let the application run for a while, it
never seems to go back down. The only reason I am using webkit is to
grab these thumbnails, which happens once, and need to be refreshed
very rarely, if ever. I'm trying to read up on how to alter the
caching behavior of WebKit now.
Thanks for the help.
Cheers,
Tim R.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden