-
Notifications
You must be signed in to change notification settings - Fork 24.2k
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
0.62 JSC hit 100% cpu in Release, not Debug #28537
Comments
Isolated cause of JSC CPU pegging to be somewhere in react-native-cached-image in my app. I'm deprecating its use to just use RN's own |
Hi, I'm facing the same issue, using the Image native component didn't solve the problem. Actually, even I'm trying with real device Iphone X and emulator, same result... But. when I run the project with iPhone 11 Pro max emulator OS 13.3, the problem is not there, the CPU is at 0%. I've searched everywhere and this is the only topic that seems to be the same issue. I need some help here. |
Hi @fungilation and thank you for your fork of react-native-cached-image! 🎉 I'm upgrading my app to RN 0.62 and I just saw that react-native-cached-image as been deprecated in favor of RN's own image but I was wondering if you managed to make RN's Images cache work on Android as the documentation says that Cache Control is only for iOS... Thanks for your response! 😊 |
Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Before upgrading, my app was on RN 0.61.5. No issue on cpu pegged at 100%.
After upgrade to 0.62.1, on certain number crunching in JS and I can't identify exactly in what yet (reason below). I'm getting 100% cpu pegged and app completely stalled from doing anything else, though UI is not frozen. This is due to JSC is completely blocked. This is when app is built in release mode, and so JSC is run on real device (iPhone X)
![image](https://user-images.githubusercontent.com/3803466/78507136-23730780-7733-11ea-87e9-e025bfb8a9ca.png)
If I rebuilt app in Debug mode, running on same real device, and doing same UX on app. No more issue as JS processing is run in Chrome's V8 instead:
![image](https://user-images.githubusercontent.com/3803466/78508818-a3529f00-773e-11ea-849b-5129b318d32f.png)
React Native version:
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
I can't list repro steps as I'm not sure what in my JS code is triggering the 100% cpu in JSC, that doesn't occur in Debug mode V8. But there's clearly something changed from RN 0.61 -> 0.62 upgrade that changed it.
And since I can't debug while the JSC cpu pegged occurs only in Release mode, this makes this a Heisenbug. How do I debug when app in debug mode doesn't manifest the same issue that's in release?
Expected Results
JSC not stalled in Release mode on device
The text was updated successfully, but these errors were encountered: