Stopping build doesn't stop build (for a while) [Xcode]
| Originator: | billymeltdown | ||
| Number: | rdar://11063017 | Date Originated: | 16-Mar-2012 11:22 AM |
| Status: | Closed | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode 4.3.1 |
| Classification: | Performance | Reproducible: | Sometimes |
16-Mar-2012 11:22 AM William Gray: Summary: When I am running an Archive build, which has a number of dependencies (like openssl, sqlcipher), and I stop the build in the middle of one of these dependent builds, with the Stop button, an error is listed, and the build appears to still be going or hung, and stays that way for a while, preventing me from getting started on the next one, etc. Steps to Reproduce: Begin an Archive build of a project with a dependency that takes a long time to build (like openssl). Press stop while Xcode is still building one of your dependencies. Expected Results: Build should stop within the next few seconds or sooner, used to all the time. Actual Results: An error shows in the heads-up-display and the build appears to hang, doesn't stop. Attaching screen clip. It's been in this state for the five minutes I've been typing this up! Regression: I don't think so, this seems to have been happening since we started using Xcode 4 and the new Archive feature. Notes: Just a general performance issue, having to try to stop the build multiple times in order to get on with, say, adjusting the version number in the plist and launching it again. Should be quick to do. Frustrating. 16-Mar-2012 11:22 AM William Gray: 'Screen Shot 2012-03-16 at 11.18.55 AM.png' was successfully uploaded
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
This ended up being closed because I didn't take an Activity Monitor sample when Xcode was misbehaving. Well, I waited too long to do it. Doesn't seem to be a problem now that I'm using Xcode 4.3.2, so it's just as well.