Who's NSDelayedCallbackCenter and why is he retaining a huge load of junk?
Who's NSDelayedCallbackCenter and why is he retaining a huge load of junk?
- Subject: Who's NSDelayedCallbackCenter and why is he retaining a huge load of junk?
- From: Miguel Arroz <email@hidden>
- Date: Tue, 23 Dec 2008 23:28:16 +0000
Hi!
I have an auxiliary application that essentially launches a thread
and waits for requests to exist on the database do process them.
During the processing, many objects are created and saved. I took
all the precautions to avoid high memory usage (like creating small
batches of objects and saving them, disposing ECs, etc). This didn't
prevent the app from using all the allocated memory and blowing up.
After some investigations, I found out that I have hundreds of
thousands of objects (mainly undo managers) retained by some
NSDelayedCallbackCenter. The docs say this guy holds some calls to be
done after the RR loop finishes.
Now, my problem is that there's no RR loop here. So... what's going
on? Do I have to manually tell the NSDelayedCallbackCenter to run the
queued selectors? How? And what exactly means "in the end of the RR
loop" if I have an app that actually handles requests and it's
handling them concurrently?
Yours
Miguel Arroz
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden