Re: XCode misbehaving on Intel
Re: XCode misbehaving on Intel
- Subject: Re: XCode misbehaving on Intel
- From: Greg Guerin <email@hidden>
- Date: Sun, 19 Nov 2006 14:56:42 -0700
Christopher Ashworth wrote:
>I recently purchased a MacBook Pro to supplement my Powerbook G4 for
>developing/testing on both Intel and PPC. I moved my project over to
>the MBP and have been having major problems with XCode 2.4.1
>misbehaving. It frequently crashes while compiling, or even just
>when opening a project. I was even seeing bizarre behavior like the
>project throwing an error and refusing to compile, followed
>immediately by a successful compile on the second attempt, with zero
>changes made to the project.
Those symptoms sound a lot like a memory problem.
How many weeks ago was "recently"? Did you add memory to the MBP?
Do you run any other memory-hungry apps on the MBP, or is Xcode the only
significant app?
If the main thing you've run is Xcode, and you haven't had the machine for
long, it's quite possible that Xcode is the only thing intensive enough to
trigger the memory failure. If you can, try running some other
memory-hungry apps and see if they crash. Or run a memory-test app
overnight.
Another possibility is to create a new project on the MBP, add your
existing files to it, and see how it builds. If it works well, that's
evidence the problem lies in the project-file. If it crashes, then it's
more likely to be memory.
The reason for using your existing files in the new project is to force a
similar amount of work to build the new project, which means Xcode would be
using a similar amount of memory. Creating a new project with one file
could be small enough that Xcode would work fine, and only barf when the
project got large enough to trigger a memory failure.
-- GG
_______________________________________________
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