• 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
Calling allObjects memory allocation problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Calling allObjects memory allocation problem


  • Subject: Calling allObjects memory allocation problem
  • From: Vassilis Pantazis <email@hidden>
  • Date: Wed, 19 May 2010 14:36:16 +0300

Hello,

I have in my code the following statement:

    NSDirectoryEnumerator* dirEnum;
    NSArray* inDirContents;

    dirEnum = [[NSFileManager defaultManager] enumeratorAtPath:inPath]; //
inPath is a valid path
    inDirContents = [dirEnum allObjects];

I have noticed that when the path contains many objects, a significant
amount of memory is allocated that is not released, neither when trying to
explicitly release inDirContents, nor when using an autorelease pool.
Can someone explain to me why this happens please and how to solve it?

Kind regards to all, this is my first mail in this list.
Vas
_______________________________________________

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: Calling allObjects memory allocation problem
      • From: Nick Zitzmann <email@hidden>
  • Prev by Date: Re: Error 134100 - Core Data models incompatible
  • Next by Date: Re: Notifications on main thread
  • Previous by thread: Re: migrating CoreData data model doesn't work
  • Next by thread: Re: Calling allObjects memory allocation problem
  • Index(es):
    • Date
    • Thread