-
Notifications
You must be signed in to change notification settings - Fork 24.6k
Cancelling offscreen image loads causing crashes in 0.33.0-rc.0 #9751
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
Resolution: Locked
This issue was locked by the bot.
Comments
I have met same crashes in RN 0.32.0 #9334 |
facebook-github-bot
pushed a commit
that referenced
this issue
Sep 28, 2016
Summary: This PR is related to the multitude of crashes (#10016, #9751, #9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR #9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes #10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
cmcewen
pushed a commit
to cmcewen/react-native
that referenced
this issue
Sep 28, 2016
Summary: This PR is related to the multitude of crashes (facebook#10016, facebook#9751, facebook#9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR facebook#9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes facebook#10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
cmcewen
pushed a commit
to cmcewen/react-native
that referenced
this issue
Sep 28, 2016
Summary: This fixes facebook#9751 We were seeing the same issues as the original reporter. I'm not an expert on this code, so apologies if it's naive, but we haven't seen the crash since making this change. From my understanding of it, it seems like the `cancelLoad` block was being released before the block returned by `_loadImageOrDataWithURLRequest:` was called. This PR checks the `cancelled` flag before calling `cancelLoad()`. Closes facebook#10016 Differential Revision: D3902723 Pulled By: javache fbshipit-source-id: 75cd115e28694105c6fc29469986998ca0d4cd09
mikelambert
pushed a commit
to mikelambert/react-native
that referenced
this issue
Sep 29, 2016
Summary: This fixes facebook#9751 We were seeing the same issues as the original reporter. I'm not an expert on this code, so apologies if it's naive, but we haven't seen the crash since making this change. From my understanding of it, it seems like the `cancelLoad` block was being released before the block returned by `_loadImageOrDataWithURLRequest:` was called. This PR checks the `cancelled` flag before calling `cancelLoad()`. Closes facebook#10016 Differential Revision: D3902723 Pulled By: javache fbshipit-source-id: 75cd115e28694105c6fc29469986998ca0d4cd09
mikelambert
pushed a commit
to mikelambert/react-native
that referenced
this issue
Sep 29, 2016
Summary: This PR is related to the multitude of crashes (facebook#10016, facebook#9751, facebook#9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR facebook#9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes facebook#10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
gre
pushed a commit
to gre/react-native
that referenced
this issue
Oct 10, 2016
Summary: This fixes facebook#9751 We were seeing the same issues as the original reporter. I'm not an expert on this code, so apologies if it's naive, but we haven't seen the crash since making this change. From my understanding of it, it seems like the `cancelLoad` block was being released before the block returned by `_loadImageOrDataWithURLRequest:` was called. This PR checks the `cancelled` flag before calling `cancelLoad()`. Closes facebook#10016 Differential Revision: D3902723 Pulled By: javache fbshipit-source-id: 75cd115e28694105c6fc29469986998ca0d4cd09
gre
pushed a commit
to gre/react-native
that referenced
this issue
Oct 10, 2016
Summary: This PR is related to the multitude of crashes (facebook#10016, facebook#9751, facebook#9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR facebook#9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes facebook#10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
grabbou
pushed a commit
that referenced
this issue
Oct 10, 2016
Summary: This PR is related to the multitude of crashes (#10016, #9751, #9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR #9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes #10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
pfeiffer
added a commit
to pfeiffer/react-native
that referenced
this issue
Oct 12, 2016
Summary: This PR is related to the multitude of crashes (facebook#10016, facebook#9751, facebook#9882). From my understanding, we should be using a strong reference when calling `decodeImageData` or we could be calling the method on a deallocated instance. PR facebook#9751 have mitigated this by adding a fail-safe, but I think the culprint is the weak reference, which this PR fixes. Tested on iOS only, since it doesn't touch Android. Closes facebook#10147 Differential Revision: D3938763 fbshipit-source-id: 7389d4ae7a98926014401a1fe0cbbdcdd5ee6a01
pfeiffer
pushed a commit
to pfeiffer/react-native
that referenced
this issue
Oct 12, 2016
Summary: This fixes facebook#9751 We were seeing the same issues as the original reporter. I'm not an expert on this code, so apologies if it's naive, but we haven't seen the crash since making this change. From my understanding of it, it seems like the `cancelLoad` block was being released before the block returned by `_loadImageOrDataWithURLRequest:` was called. This PR checks the `cancelled` flag before calling `cancelLoad()`. Closes facebook#10016 Differential Revision: D3902723 Pulled By: javache fbshipit-source-id: 75cd115e28694105c6fc29469986998ca0d4cd09
This is still happening for us on 0.35.0 |
This issue was closed.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Issue Description
I'm using RN 0.33.0-rc.0 and have a standard list view that continues to load more rows (using Relay) as the user scrolls down:

If you scroll through the list on device (iPhone 6S) I'm frequently seeing crashes - all look to be related to the cancelling of loading images once the view has gone off screen.
Crash Traces





Expected Results
Deallocated instances not called or instances to be retained
Additional Information
The text was updated successfully, but these errors were encountered: