Hi Bridger-
I had precisely the same issue some months ago, and wrote to this
list. I did get a response off-list from an Apple engineer that
mentioned that this was a known problem and there was no workaround at
present. Not sure if things have changed since then (although perhaps
they have, as I was seeing the same problem on the Intel side as the
PPC). I ended up returning to managing my own memory, as I needed the
DO in the implementation I was working on.
Anyone have more recent info?
John
Positive Spin Media
http://www.positivespinmedia.com
On Dec 13, 2008, at 12:26 PM, Bridger Maxwell wrote:
Hey,
I am working on a networking system that uses distributed objects.
This is a
large collaboration between students, and I thought garbage
collection would
be perfect for new Cocoa programmers, so we wouldn't have to deal with
memory management quite yet. The network will be a mix of Intel and
PPC, so
there is another complication too.
Everything seems to work on Intel, it is on PPC that we have the
problems.
When we first make the connection to the server, we can message the
remote
object just fine. It is when we try to message the distant object at
later
times that we get errors. This sounds enough like a memory management
problem. Sure enough, when turn off garbage collection, and add in the
proper retain calls, it seems to function fine. Does distributed
objects
work with garbage collection (on PPC)? Here are some of the errors I
am
getting.
Console output:
2008-12-13 11:42:02.204 StationTerminal[715:10b] *** -
[NSAutoreleasePool
objectForKey:]: unrecognized selector sent to instance 0x10610c0
2008-12-13 11:42:02.222 StationTerminal[715:10b] Exception name:
NSInvalidArgumentException Reason: *** -[NSAutoreleasePool
objectForKey:]:
unrecognized selector sent to instance 0x10610c0
2008-12-13 11:42:02.225 StationTerminal[715:10b] *** -[NSLock lock]:
deadlock (<NSLock: 0x1061040> '(null)')
2008-12-13 11:42:02.227 StationTerminal[715:10b] *** Break on
_NSLockError()
to debug.
Note here, that NSAutoreleasePool is getting objectForKey:, as if it
were a
dictionary. It is not always NSAutoreleasePool getting the message,
we have
also got NSCFDataType and some internal color-related class
receiving this
message, among others. Sound enough like a memory mangement issue?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
