On Feb 22, 2013, at 5:52 PM, Mr. Gecko wrote:
> On Feb 22, 2013, at 10:47 AM, Willeke wrote:
>
>> I don't know why but it doesn't leak if you do readInBackgroundAndNotify
>> only if [data length]!=0.
>
> Doesn't make sense as when you release the NSPipe, it should disable that. I
> will repor
Doesn't make sense as when you release the NSPipe, it should disable that. I
will report this to apple via Rdar.
Thanks for solving my issue!
On Feb 22, 2013, at 10:47 AM, Willeke wrote:
> I don't know why but it doesn't leak if you do readInBackgroundAndNotify only
> if [data length]!=0.
>
I don't know why but it doesn't leak if you do readInBackgroundAndNotify only
if [data length]!=0.
- Willeke
Op 20 feb 2013, om 23:56 heeft Mr. Gecko het volgende geschreven:
> Looks like every pipe is leaking. I cannot see a way to prevent the leak
> myself as I know the NSPipes are being r
I take that back, it still crashes with ARC… It crashes at run 4720.
___
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.co
Looks like every pipe is leaking. I cannot see a way to prevent the leak myself
as I know the NSPipes are being released. It doesn't seem to crash with Auto
Reference Counting… But boy, it eats memory and still leaks. So I would think
this is an Apple bug.
On Feb 20, 2013, at 4:31 PM, Ken Thoma
On Feb 20, 2013, at 4:10 PM, Mr. Gecko wrote:
> I have written a daemon that listens for an incoming connection, runs a
> process using NSTask, and sends the output to the connection. After a couple
> of hours of receiving connections at varying lengths of time… The system has
> all of it's pip
I have written a daemon that listens for an incoming connection, runs a process
using NSTask, and sends the output to the connection. After a couple of hours
of receiving connections at varying lengths of time… The system has all of it's
pipes taken, and the process stops sending responses to th
