Re: Distributed Objects with Garbage Collection (on PPC)
Re: Distributed Objects with Garbage Collection (on PPC)
- Subject: Re: Distributed Objects with Garbage Collection (on PPC)
- From: Bill Bumgarner <email@hidden>
- Date: Sat, 13 Dec 2008 12:00:11 -0800
On Dec 13, 2008, at 11:26 AM, Bridger Maxwell wrote:
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.
Distributed Objects, in general, is very tricky.
It sounds like you are running into a situation where the differences
between the way the stacks are managed on Intel vs. PPC means that an
object is being rooted on the Intel side on the stack that isn't being
rooted on PPC. This could happen for a number of legitimate reasons.
Specifically, it sounds like some object was being reaped too early by
the collector. This is most likely because:
- the pointer is hidden by being off alignment in a structure or
having been XORed with something for some tricksy reason.
- the pointer has wandered into unscanned memory and, thus, the
collector no longer sees the reference
Or it could simply be case of a memory smasher and you are getting
lucky on Intel.
Do you know what dictionary is being reaped prematurely? Is it one
of yours or from the infrastructure?
b.bum
_______________________________________________
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