You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use ASNodeController throughout our app, and after upgrading to 2.8, I'm seeing a deadlock in one of our node controllers. It seems to have started after this pull request was merged in: #1179
Commenting out the ASLockScopeSelf in ASNodeController implementation file does fix the issue
Removing a reference to flowLayout and instead just passing UICollectionViewLayout() in the collection initialization
moving some of the node configuration out of createNode and into nodeDidLoad
The text was updated successfully, but these errors were encountered:
stephensilber
changed the title
ASNodeController (post-NSLocking) is causing deadlock
ASNodeController (post-NSLocking) is causing deadlock in 2.8
Feb 15, 2019
We use
ASNodeController
throughout our app, and after upgrading to2.8
, I'm seeing a deadlock in one of our node controllers. It seems to have started after this pull request was merged in:#1179
It looks like @appleguy may have brought this up as a potential problem in the #1179 PR review.
https://github.com/TextureGroup/Texture/pull/1179/files/83696de05cc03e6ced2a76780b8a03f1442b0b92#diff-201f20cb04a043f825170266014a5b25R42
Here's my node controller:
Things I have tried:
ASLockScopeSelf
in ASNodeController implementation file does fix the issueflowLayout
and instead just passingUICollectionViewLayout()
in the collection initializationcreateNode
and intonodeDidLoad
The text was updated successfully, but these errors were encountered: