Apple

On Mar 19, 2007, at 11:00 AM, Greg Guerin 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.

We've done all this and have found it's a deadlock in Rez itself. It's usually encountered when invoking multiple copies of Rez simultaneously but could theoretically happen any time that some other process opens a file Rez is reading it. We've addressed this in Xcode 3.0 but it can usually be worked around in previous versions by making sure your project isn't trying to Rez two files in parallel. That's why having the full build transcripts would be helpful.

References:
	>Re: rezzing forever (From: Greg Guerin <email@hidden>)