FROM : John Pannell
DATE : Mon Jun 30 20:57:29 2008
Hi there-
I encountered the same issue some months ago, and posted my questions
to this list. An Apple engineer did reply off-list that this was a
known issue with garbage collection and that there was no known
workaround at that time.
I was just playing with GC for fun and reverted back to "regular"
memory management.
You might inquire of Apple DTS if things have changed at all; my
incident was in the 10.5.0 days.
John
John Pannell
http://www.positivespinmedia.com
On Jun 30, 2008, at 11:33 AM, <email_removed> wrote:
> hey,
> I have a project that uses Bonjour for some of its communication,
> theres a server and a client, and I was having tremendous difficulty
> getting it to work, pouring and pouring over my code, only to
> discover some weeks later that for some odd reason, NSConnections do
> not work when the project is set to support or require garbage
> collection.
>
> As a test I set garbage collection to: Unsupported, and the app
> compiled, and the NSConnection returned the proxy object as
> expected. But the app obviously failed to do much else, because I
> had no retain, release, or autorelease method calls.
>
> can anybody shed any light on this? am I really stuck managing the
> memory myself? This is intolerable.
DATE : Mon Jun 30 20:57:29 2008
Hi there-
I encountered the same issue some months ago, and posted my questions
to this list. An Apple engineer did reply off-list that this was a
known issue with garbage collection and that there was no known
workaround at that time.
I was just playing with GC for fun and reverted back to "regular"
memory management.
You might inquire of Apple DTS if things have changed at all; my
incident was in the 10.5.0 days.
John
John Pannell
http://www.positivespinmedia.com
On Jun 30, 2008, at 11:33 AM, <email_removed> wrote:
> hey,
> I have a project that uses Bonjour for some of its communication,
> theres a server and a client, and I was having tremendous difficulty
> getting it to work, pouring and pouring over my code, only to
> discover some weeks later that for some odd reason, NSConnections do
> not work when the project is set to support or require garbage
> collection.
>
> As a test I set garbage collection to: Unsupported, and the app
> compiled, and the NSConnection returned the proxy object as
> expected. But the app obviously failed to do much else, because I
> had no retain, release, or autorelease method calls.
>
> can anybody shed any light on this? am I really stuck managing the
> memory myself? This is intolerable.






Cocoa mail archive

