Re: XCode build gets stuck if simultaneously indexing
Re: XCode build gets stuck if simultaneously indexing
- Subject: Re: XCode build gets stuck if simultaneously indexing
- From: "Wood, Tobias" <email@hidden>
- Date: Thu, 11 Oct 2012 09:32:28 +0000
- Thread-topic: XCode build gets stuck if simultaneously indexing
On 11 Oct 2012, at 09:56, Wood, Tobias wrote:
> On 11 Oct 2012, at 00:07, Jean-Daniel Dupas wrote:
>
>>
>> Le 10 oct. 2012 à 17:20, Fritz Anderson <email@hidden> a écrit :
>>
>>> On 10 Oct 2012, at 8:23 AM, "Wood, Tobias" <email@hidden> wrote:
>>>
>>>> in the last couple of days I have begun experiencing an intermittent but very annoying problem with XCode (Both 4.5 and 4.5.1). If I manage to start a build at roughly the same point XCode begins Indexing my workspace, both will get stuck and fail to complete, with no way to stop either. The "Indexing" process just shows "0 of 1 files", while if I view the build log the last successful action was "Touching" a framework. Trying to start a new build (Ctrl-B) brings up a dialog informing me that one is in progress, and asks if I'd like to stop it. If I click "Stop", the button becomes greyed out but the dialog does not disappear.
>>>>
>>>> The only workaround I have found is to Force Quit XCode and then reboot. Re-opening XCode after the Force Quit will result in the same problem occurring as soon as I attempt to build, whereas rebooting will let me continue for a while until the problem starts again. Looking at the output of top in a terminal window shows that XCode has is using some CPU, but frequently ends up in a "stuck" state (instead of "running").
>>>>
>>>> This appears to be similar to this bug: http://openradar.appspot.com/10974135 which unfortunately has no solution yet.
>>>>
>>>> Has anyone else experienced this issue and found a workaround? This is a moderately complicated workspace (each project has its own git repository, and the project I am building includes one of the other projects as a git sub-module), but it has been working fine until the last couple of days.
>>>
>>> Have you tried selecting the workspace in the Projects organizer, and clicking Delete… for the Derived Data folder?
>>
>>
>> If this is the bug I know, there is absolutely nothing you can do about it. This is a deadlock in the fs kernel implementation where locks are hold by a zombie clang processes (on close() system call).
>>
>> I have reported this bug with full stackshot (userspace and kernel stack trace of all running processes) some times ago, but it look like this is not a bug that can easily be fixed.
>>
>> Trying to delete the culprit file even with a rm command will result in a lock too, and you will be force to kill the rm process.
>>
>> I saw this bug only with multi-projects workspace though.
>>
>> -- Jean-Daniel
>
> This would appear to be the same bug. It happened again yesterday without the indexing (the build just got stuck by itself) and I have also seen the zombie clang processes (sometimes with an extra zombie XCode and ibtool). I previously tried rm on the culprit files, but that resulted in an rm process that couldn't be killed as well! I have now tried deleting the Derived Data folder just to see if that helps.
>
> I have also filed a bug report with Apple. It is pretty strange though - I've been using this multi-project workspace for weeks without problems, this has only started happening in the last few days.
>
> Thanks for your help,
> Toby Wood
Just for posterity - deleting the Derived Data folder has not helped.
Toby
_______________________________________________
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