Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-2281] Xcode crash with 08/04 snapshot #44888

Closed
swift-ci opened this issue Aug 4, 2016 · 4 comments
Closed

[SR-2281] Xcode crash with 08/04 snapshot #44888

swift-ci opened this issue Aug 4, 2016 · 4 comments

Comments

@swift-ci
Copy link
Collaborator

@swift-ci swift-ci commented Aug 4, 2016

Previous ID SR-2281
Radar None
Original Reporter clane47 (JIRA User)
Type Bug
Status Closed
Resolution Cannot Reproduce
Environment

Late 2012 iMac with Core i7 processor
32 GB ram

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, 3.0Regression, CompilerCrash
Assignee clane47 (JIRA)
Priority Medium

md5: fd541a3c922dc71aa746e20459bfa12e

Issue Description:

1. Build a new iOS Master/Detail project with core data option checked
2. Fix the minor errors that appear from using the new toolchain
3. After replacing AnyObject? with Any in the prepare for segue function, Xcode crashes when trying to build.

@belkadan
Copy link
Contributor

@belkadan belkadan commented Aug 5, 2016

Mind attaching the project? I want to make sure "fix the minor errors" is carried out in the same way.

@swift-ci
Copy link
Collaborator Author

@swift-ci swift-ci commented Aug 5, 2016

Comment by Charles Lane (JIRA)

Jordan, sorry, the project no longer fails. After starting up my computer this morning the project compiles just fine. It may have to do with the fact that I'm also running macOS Sierra beta.
Next time I'll do a restart before I start panicking!
I don't know if I'm supposed to close this issue or if you prefer to do it.

@belkadan
Copy link
Contributor

@belkadan belkadan commented Aug 5, 2016

The general policy is that Resolved means we Swift people think the issue is fixed, and Closed means you think it's fixed. So it's okay to close.

@swift-ci
Copy link
Collaborator Author

@swift-ci swift-ci commented Aug 5, 2016

Comment by Charles Lane (JIRA)

Issue resolved just by restarting the computer. Strange since no other projects were affected!

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants