• 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: copyItemAtPath takes double time than the Finder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: copyItemAtPath takes double time than the Finder


  • Subject: Re: copyItemAtPath takes double time than the Finder
  • From: "Gary L. Wade" <email@hidden>
  • Date: Wed, 19 Jan 2011 15:49:15 -0800
  • Thread-topic: copyItemAtPath takes double time than the Finder

Both FSCopyObjectAsync and FSCopyObjectSync leak memory in Mac OS X
10.6.x, even up to 10.6.6; the async form leaks even more than the sync
form.  Apple has verified this both in my bug, rdar://8734968 (opened
against 10.6.5) and another unspecified one opened earlier in 2010.  I've
verified both still leak memory in 10.6.6.

If you are only doing one or two copies per execution of your application,
the leak is not significant.  If you are doing many copies per execution
of your application (as I must), these leaks are horrible.

Apple has verified there is nothing a developer can do to work around this
other than to use the Cocoa method.

On 01/19/2011 3:15 PM, "Mike Abdullah" <email@hidden> wrote:

>Well you shouldn't be using this synchronous API for long-running copy
>operations, since it can't be cancelled or give progress.
>
>Instead use FSCopyObjectAsync().
>
>On 19 Jan 2011, at 21:42, Leonardo wrote:
>
>> Hi,
>> I have checked, the Finder, takes only 7 seconds to copy a 500MB dmg
>>file.
>> The copyItemAtPath API takes 18 seconds to copy the same file.
>> Why? Is a way to make copyItemAtPath run at the same Finder speed?
>> If not, which API should I use to get the same performance?
>>
>> I use:
>>    [[NSFileManager defaultManager] copyItemAtPath:src toPath:dst
>>        error:&err];
>>
>> Architectures: ppc, i386
>> Base SDK: Mac OS X 10.5
>> Valid Architectures: i386 ppc ppc64 ppc7400 ppc970 x86_64
>> C/C++ Compiler Version: GCC 4.2
>> Optimization Level: Fastest [-O3]
>>
>>
>> Regards
>> -- Leonardo
>>
>>
>> _______________________________________________
>>
>> 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:
>>
>>net
>>
>> This email sent to email@hidden
>
>_______________________________________________
>
>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:
>s.com
>
>This email sent to email@hidden


_______________________________________________

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

  • Follow-Ups:
    • Re: copyItemAtPath takes double time than the Finder
      • From: Peter Lübke <email@hidden>
References: 
 >Re: copyItemAtPath takes double time than the Finder (From: Mike Abdullah <email@hidden>)

  • Prev by Date: Re: Odd Crash when adding table columns manually
  • Next by Date: Re: Odd Crash when adding table columns manually
  • Previous by thread: Re: copyItemAtPath takes double time than the Finder
  • Next by thread: Re: copyItemAtPath takes double time than the Finder
  • Index(es):
    • Date
    • Thread