On 04/09/09 10:38 AM, "Gerriet M. Denkmann" wrote:
>
> But it fails to mention, what I should use instead.
> Any ideas?
Take a look at serviceConnectionWIthName:rootObject:, new in 10.5.
***
This e-mail and its attachments ar
> The first thing it should do in main() is invoke
> objc_startCollectorThread() (from ) which will
> ensure GC is happening asynchronously, rather than only when the
> autorelease pool is drained.
Thank you.
I added the call to objc_startCollectorThread() and my simple sample no
longer leaks memo
On 07/08/09 5:30 PM, "Quincey Morris" wrote:
> On Aug 7, 2009, at 14:06, Tim Murison wrote:
>
>> The improved code will execute about 1000 operations as quickly as
>> possible,
>> then it will sleep for 1 second. Before sleeping, it will print the
>>
>> With GC, the memory use grows forever, without GC, it doesn't grow at all.
>> Instruments tells me the garbage collector is responsible for allocating the
>> leaking memory from within the collection routine, I think maybe instruments
>> is confused, but it does confirm that the live object coun
On 07/08/09 4:33 PM, "Quincey Morris" wrote:
> On Aug 7, 2009, at 13:05, Tim Murison wrote:
>
>> In my real application I have a memory leak that I can trace to
>> operations
>> not being release by the operation queue. This program is meant to
>> s
> 'setMaxConcurrentOperationCount' specifies the number of concurrently
> executing threads. I don't see anything in the documentation that
> guarantees it will control the number of concurrently existing
> threads. Threads may exist waiting to execute, and threads will exist
> for some period of t
> Convenience constructors should autorelease objects they allocate.
>
But I'm using GC, so that can't be my problem right?
***
This e-mail and its attachments are confidential, legally privileged, may be
subject to copyrig
Hi Cocoa gurus,
I'm running on Leopard 10.5.7 (and Snow Leopard, but that's a different
problem!) and have been seeing some strange behaviour with NSOperationQueue.
I know about the crash in 10.5.6 and earlier, but this doesn't seem to be
related to that crash.
The code is below and was compiled
> OK, thank you. Is it possible, would you happen to know, for an application
> to verify its own signature? I do this on Windows (using WinVerifyTrust) to
> check that the code has not been tampered with. Can't trust anybody these
> days :)
>
It is possible, but the APIs to code-signing are p
>>> So do I just create self-signed certificate and select it in the Xcode
>>> build settings and that's it? Everything is as desirable and as
>>> functional as need be?
>
>> Pretty much. Although in future versions Apple may elect to nag if the
>> certificate is not signed by a trusted root autho
> So do I just create self-signed certificate and select it in the Xcode
> build settings and that's it? Everything is as desirable and as
> functional as need be?
Pretty much. Although in future versions Apple may elect to nag if the
certificate is not signed by a trusted root authority.
___
Hi,
I noticed an issue in my code related to NSFileManager. When running my
program with gmalloc, I got a seg fault. I traced the cause back to
NSFileManager and wrote a simple reproducible program to illustrate the
issue. Can one of the gurus here point out a flaw, or is this a real bug?
#import
>> Since UDSs are bidirectional, I don't need an explicit receivePort. The
>> documentation for NSConnection states that if receivePort is nil, then a
>> port of the same type as sendPort will be automatically created. My guess is
>> that this is done to provide support for distributed objects over
Hi,
I've been working with distributed objects for the last few days and came
across a behaviour in NSConnection that seems to be a bug, or at least
sub-optimal.
My client application communicates with the server using Unix Domain
Sockets. After creating a properly configured NSSocketPort (sendPo
14 matches
Mail list logo
