-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
CameraRollExample crashes and reboots iPhone 6 #779
Comments
That's because ScrollView is a beast! |
OK, seriously, does it crash in the UI explorer example or is this just your implementation that's crashing? |
it crashes the UIExplorer on the device. On the simulator, I haven't tested with more than a handful of images. I'll do that now though. |
So far, testing in the simulator with 10 images generates the same warnings, but no memory error or crash. The scrolling is pretty jerky: https://www.youtube.com/watch?v=YSMo1-2b1Qw |
Having the same problem with UI explorer and in my own app. Tested in on an iPhone 5S with iOS 8.3
|
Well as far as i tests this issue it's an memory problem. https://github.com/facebook/react-native/blob/master/Libraries/Image/RCTImageLoader.m#L48 UIImage *image = [UIImage imageWithCGImage:[representation fullResolutionImage] scale:1.0f orientation:(UIImageOrientation)orientation]; I would like to propose an attribute to Image to suggest the loading of the asset Thumbail. but i'm not fan of that. I think the issue is more complex than that. I's an architecure one. for thumb we need to use this method UIImage *image = [UIImage imageWithCGImage:[asset thumbnail]]; Feel free to talk about it |
This is also occurring for me... intermittently while scrolling in the simulator in my own app. |
Hi all Thanks |
Dup #902 |
Testing this component on an iPhone 6, also with a trimmed down implementation, causes a crash and occasional reboot.
Here's what I can see in the Xcode error window: "Warning: ScrollView doesn't take rejection well - scrolls anyway"
Any better way to debug?
The text was updated successfully, but these errors were encountered: