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

EXC_BAD_ACCESS Crashes occur in xcode15 #879

Closed
eunyongeom opened this issue Oct 5, 2023 · 4 comments
Closed

EXC_BAD_ACCESS Crashes occur in xcode15 #879

eunyongeom opened this issue Oct 5, 2023 · 4 comments

Comments

@eunyongeom
Copy link

eunyongeom commented Oct 5, 2023

After updating to xcode15, the following crashes occur.
Due to these problems, I am unable to update to xcode15.
I would greatly appreciate your help.

  1. duringLifetimeOf crash
extension Signal {
	/// Forward events from `self` until `object` deinitializes, at which point the
	/// returned signal will complete.
	///
	/// - parameters:
	///   - object: An object of which the deinitialization would complete the returned
	///             `Signal`. Both Objective-C and native Swift objects are supported.
	///
	/// - returns: A signal that will deliver events until `object` deinitializes.
	public func take(duringLifetimeOf object: AnyObject) -> Signal<Value, Error> {
		return take(during: Lifetime.of(object))
	}
}
Screenshot 2023-10-05 at 11 40 07 PM
  1. tryToDisposeSilentlyIfQualified crash
Screenshot 2023-10-07 at 1 25 52 PM
@eunyongeom eunyongeom changed the title duringLifetimeOf crash on Swift 5.9(Xcode15) duringLifetimeOf crash on Xcode15 Oct 6, 2023
@eunyongeom eunyongeom changed the title duringLifetimeOf crash on Xcode15 Crashes that occur in xcode15 Oct 7, 2023
@eunyongeom eunyongeom changed the title Crashes that occur in xcode15 EXC_BAD_ACCESS Crashes that occur in xcode15 Oct 8, 2023
@eunyongeom eunyongeom changed the title EXC_BAD_ACCESS Crashes that occur in xcode15 EXC_BAD_ACCESS Crashes occur in xcode15 Oct 8, 2023
@eunyongeom
Copy link
Author

I think the problem occurred because I built it incorrectly.
After rebuilding it, the crash problem went away.

@mluisbrown
Copy link
Contributor

Thanks for the update @eunyongeom. There is a known issue with incremental compilation of Swift since Xcode 14 which can cause random EXC_BAD_ACCESS crashes if a struct or other data type is altered to occupy more memory (eg adding an extra field) than before. The solution is to do a clean build.

@eunyongeom
Copy link
Author

eunyongeom commented Oct 11, 2023

@mluisbrown
Thank you for your reply.
Does this issue only occur in ReactiveSwift?
Or is it a problem that other libraries can also occur?

@mluisbrown
Copy link
Contributor

This issue can occur in any project. People using the Composable Architecture also see it a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants