• 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: The thread that starts by NSTask didn't clear up
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The thread that starts by NSTask didn't clear up


  • Subject: Re: The thread that starts by NSTask didn't clear up
  • From: Etienne Guérard <email@hidden>
  • Date: Wed, 10 Dec 2008 10:46:07 +0100

Hi,

On Dec 10, 2008, at 2:26 AM, Xianyu_Ge wrote:

thanks for your reply. I means in my project, I want to use NSTask to launch an application, and send application some parameters, when use NSTask launch application that will add a new thread, right?

As far as I understand, you use NSTask to launch your application. But this does not imply that a new thread is created to monitor the launched process, unless of course, if you setup your own thread to monitor the process.
So I think you assume that NSTask will use a thread but this is wrong. NSTask is just a wrapper around execve(), no threading involved here.


and then send Apple event, when application received Apple event , it will quit, usually, the thread starts by NSTask will exit, because the application had quit, so I don't understand this, if use NSTask launch application more times, thread count will always increased, even if application had quit. I appreciate that any reply, thank you very much.

You can use ThreadViewer to convince yourself that there's no threading involved by using NSTask.


EG


--- Best Regards, Xianyu

On Dec 10, 2008, at 12:44 AM, Etienne Guérard wrote:

I started an AP use NSTask in my project ,when I loaded this AP, thread count will be increased ,after sending apple event to AP , and AP will exit, but thread count can't decrease. If I used this method load AP more times, thread count will increased, but there was no problem on tiger, just present leopard. Sorry for my poor english.

I assume that "AP" acually means "application".
I understand that you send some Apple event to your application like a "quit' event, right?
You say that your application exit. OK. So what process the threads you're talking about belong to?
Where does NSTask come into this?


You have to be more precise to get an answer...

EG

------------------------------------------------------------
This message and any attachments (the "message") are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither DxO Labs nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. DxO Labs et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, modifie ou falsifie.

_______________________________________________

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: 
 >The thread that starts by NSTask didn't clear up (From: Xianyu_Ge <email@hidden>)
 >Re: The thread that starts by NSTask didn't clear up (From: Etienne Guérard <email@hidden>)
 >Re: The thread that starts by NSTask didn't clear up (From: Xianyu_Ge <email@hidden>)

  • Prev by Date: Re: How to detect a paste request for file copy/paste?
  • Next by Date: Problems with multiple selection and NSArrayController
  • Previous by thread: Re: The thread that starts by NSTask didn't clear up
  • Next by thread: Re: The thread that starts by NSTask didn't clear up
  • Index(es):
    • Date
    • Thread