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

Caishen causing crash #136

Open
korovyev opened this issue Feb 27, 2018 · 0 comments
Open

Caishen causing crash #136

korovyev opened this issue Feb 27, 2018 · 0 comments

Comments

@korovyev
Copy link

It seems something is keeping a strong reference to CardTextField and is not releasing it

It then still seems to be registered for some internal notification that tries to access its superview, which it might not have at that point, causing crash. (In our case this is caused by a call to .setContentOffset(.. on a collectionView)

Heres the call stack
screen shot 2018-02-27 at 14 41 48

And heres a screenshot of the memory graph showing the textfields still in memory after the view controller in which they reside is released
screen shot 2018-02-27 at 14 42 08

Heres a sample project demonstrating the crash:
CaishenCrash.zip

Steps to reproduce in the demo project:

  • Build & Run
  • Tap button labelled "push vc"
  • On the next viewcontroller, do not tap in the CardTextField (doing so prevents the crash ... ? )
  • Tap button labelled "back"
  • Tap button labelled "crash"
  • Observe crash

Also, in our crashlytics data, this only seems to be happening on iOS 11 too, for some reason.

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

1 participant