• 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
Xcode 4.3.1 memory usage
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode 4.3.1 memory usage


  • Subject: Xcode 4.3.1 memory usage
  • From: Brad Oliver <email@hidden>
  • Date: Mon, 12 Mar 2012 21:50:12 -0700

I hate to interrupt the 10.7 love-fest but I'd like to talk about Xcode for a minute. ;-)

Over the course of a day, Xcode 4.3's memory usage creeps up from roughly 523 MB from a fresh launch with my workspace opened, to somewhere north of 7GB after several hours of work.

More interestingly, closing my workspace does not free that memory - Xcode still holds on to that 7+ GB of real memory.

I have an 8-core Mac Pro with 16 GB of RAM. Maybe you can see where this is headed.

When I compile my app, Clang fires up 8 instances. On some of my larger source files, the Clang instances will take somewhere around 1 to 1.7 GB each. If you do the math, you'll see that with 8 cores, that works out to under 16 GB.

Everything works fine until the early afternoon, when Xcode has started to bloat out. When it comes close to 7 GB of usage, my full compiles now introduce massive paging.

The problem is only solved by my quitting and relaunching Xcode.

So two questions:

1. What is causing Xcode to need *so much memory* as my day goes on? Is this a bad memory leak or by design?

2. If this is by design, why doesn't closing my workspace (and anything else I have open) free up this memory? Related, is there some way I can tell Xcode to eject whatever it's caching before I start a build (maybe as a behavior) so that I can proactively avoid all this paging?

It crossed my mind to try and force Xcode to run as 32-bit to limit its greediness to 4GB, but it seems it's 64-bit all the way now.

I'm perversely curious how high I can get Xcode's memory usage, but practical matters (such as needing to compile things) prevent that experiment for now. ;-)

--
Brad Oliver
email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Xcode 4.3.1 memory usage
      • From: Alex Zavatone <email@hidden>
    • Re: Xcode 4.3.1 memory usage
      • From: Seth Willits <email@hidden>
    • Re: Xcode 4.3.1 memory usage
      • From: Jens Alfke <email@hidden>
  • Prev by Date: Re: iOS 5.1 SDK for Xcode 4.2 for Snow Leopard?
  • Next by Date: Re: Xcode 4.3.1 memory usage
  • Previous by thread: Exporting app with Developer ID breaks Spotlight importer
  • Next by thread: Re: Xcode 4.3.1 memory usage
  • Index(es):
    • Date
    • Thread