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

Crash in JSCExecutor.cpp when reloading JS on error (iOS) #15716

Closed
VinDeng opened this issue Aug 31, 2017 · 1 comment
Closed

Crash in JSCExecutor.cpp when reloading JS on error (iOS) #15716

VinDeng opened this issue Aug 31, 2017 · 1 comment
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@VinDeng
Copy link

VinDeng commented Aug 31, 2017

Using commas + R or click reload when in the red error message screen has chance to make it crash.

Code due to crash:
path: /#rootpath/react-native/third-party/glog-0.3.4/src/logging.cc

static void logging_fail() {
#if defined(_DEBUG) && defined(_MSC_VER)
  // When debugging on windows, avoid the obnoxious dialog and make
  // it possible to continue past a LOG(FATAL) in the debugger
  _asm int 3
#else
  abort();
#endif
}

Since I build In Debug Environment, I guess the problem is I did not use VS IDE.

Xcode: 8.3.3
Simulator: iPhone 7 Plus - iOS 10.3
React Native: 0.47.2

@hramos
Copy link
Contributor

hramos commented Aug 31, 2017

Hey, thanks for reporting this issue!

It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.

I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

@hramos hramos closed this as completed Aug 31, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Aug 31, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants