Re: rezzing forever
Re: rezzing forever
- Subject: Re: rezzing forever
- From: Greg Guerin <email@hidden>
- Date: Mon, 19 Mar 2007 11:00:45 -0700
Micah Sharp wrote:
>Dual 2Ghz G5. Tried setting to only 1 CPU but unfortunately it didn't help.
>Darn, not sure why my MacBookPro is no problem.
Try applying the performance tools, like Sampler or Shark, to Rez when it's
rezzing forever. If you can see details of what it's doing forever, you
may be able to figure out how to stop it from happening.
Also see 'lsof' to discover what files Rez has open. That may also provide
clues.
If nothing provides a clue, start at zero and add successively less trivial
.r files until it fails. If it fails with nothing at all in Xcode, see if
you can get it to fail at a Terminal command-line.
In other words, apply standard diagnostic and debugging procedures that
successively narrow down the scope of where the problem could be.
>This machine was fine with .r files until a week ago or so, and is actually
>our build machine. Can't remember what changed.
Why are backups and/or change-logs so often seen as unnecessary...
Except with hindsight?
That's partly rhetorical but partly practical, too.
I've been there myself, more than once, and every time I think the pain of
the lesson will make me more cautious in the future. It does for a while,
but it doesn't stick. There's something about the pain of the last time
the lesson is taught that makes it fade, or maybe there's a communicable
disease that makes people throw caution to the wind when doing random
changes to critical machines.
If it ends up at the last resort of reinstalling Xcode or the OS, maybe
it's a painful lesson learned once and learned well, and possibly a warning
to others. Or not.
-- 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