it loads a website, to see if there are changes to the website, it
then does a lot of work, the large memory things, like the
"webView" are just one instance, and are not deallocating... (uses
just that one instance over and over again, not making new ones) so
that i don't think is the problem... (or maybe even if the instance
is allocated just once, does reloading a webView do any thing that
makes it write to memory?)
and then all the little stuff of allocating for a small variable, is
adding up each time, i really don't want to make every variable
global... but if that is proper technique, then i'll do that...
are we saying there is no way to make a process use real memory?
Jon.
On Oct 10, 2009, at 9:04 AM, Michael Dautermann wrote:
You'd probably get a much more thorough & better answer from the
list if you elaborated on what the ultimate goal of that repeating
process is.
_______________________________________________
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
