• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTask setStandardOutput bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTask setStandardOutput bug?


  • Subject: Re: NSTask setStandardOutput bug?
  • From: Chris Parker <email@hidden>
  • Date: Thu, 20 Dec 2007 19:25:56 -0800


On Dec 20, 2007, at 6:58 PM, Jerry Krinock wrote:

I believe the underlying problem is that you're exceeding the system limit on open file handles.

But the local autorelease pool that John suggested should fix it.

It will, or explicitly calling "close" on the NSFileHandle will also fix it.


File descriptors are a scarce resource; while an NSFileHandle will close its fd when it's dealloc'd, it's better to close it yourself when you know you're done with it.

.chris

--
Chris Parker
Cocoa Frameworks
Apple Inc.

_______________________________________________

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


References: 
 >NSTask setStandardOutput bug? (From: justin webster <email@hidden>)
 >Re: NSTask setStandardOutput bug? (From: John Stiles <email@hidden>)
 >Re: NSTask setStandardOutput bug? (From: Jerry Krinock <email@hidden>)

  • Prev by Date: NSFileWrapper (directory) and internal folders
  • Next by Date: Re: NSTask setStandardOutput bug?
  • Previous by thread: Re: NSTask setStandardOutput bug?
  • Next by thread: Re: NSTask setStandardOutput bug?
  • Index(es):
    • Date
    • Thread