React Native debugging - Maximum call stack size exceeded #900

nanandn · 2016-11-22T02:01:42Z

Issue and Steps to Reproduce

Starting the debugger from nuclide and attaching to it results in "Maximum call stack size exceeded" error.

Create a sample app using react-native init.
Start the react native packager in nuclide
Start the debugger in nuclide
Start the application - react-native run-ios
Start Remote JS Debugging from IOS simulator

Versions

Atom: 1.12.4
Nuclide: 0.183.0
Client OS: macOS 10.12.1

Additional Details

Installed packages (apm ls --installed):

├── atom-beautify@0.29.13
├── atom-formatter-jsbeautify@1.1.2
├── atom-material-ui@1.3.6
├── autoclose-html@0.23.0
├── git-plus@5.25.3
├── haskell-grammar@0.4.0
├── highlight-selected@0.11.2
├── language-babel@2.48.4
├── language-ini@1.16.0
├── language-ocaml@1.1.2
├── language-swift@0.5.0
├── language-thrift@1.0.2
├── merge-conflicts@1.4.4
├── nuclide@0.183.0
├── nuclide-format-js@0.0.36
├── sort-lines@0.14.0
└── tool-bar@1.0.1

The text was updated successfully, but these errors were encountered:

Marco62 · 2016-11-23T17:13:38Z

I have the same problem too!

matthieugayon · 2016-11-25T15:08:17Z

same here

TLadd · 2016-11-27T03:18:40Z

I had this issue as well; I was using the latest node version (v7.1.0).
I switched back to v6.3.0 (imagine other versions off 6 would work too, and it worked.

nanandn · 2016-11-27T17:55:37Z

I tried using node v6.9.1. I still see the problem. Doesn't atom have it own node installation? Do I need to change that to use 6.x?

mithunm93 · 2016-11-28T21:26:59Z

I'm having the same issue. I tried switching my node version to 6.4.0, but no luck because as @nanandn mentioned, atom and apm have their own node installations. @TLadd which node version did you change? If it's the version of atom, how did you do it?

$ apm -v
apm  1.12.9
npm  3.10.5
node 4.4.5
python 2.7.10
git 2.9.3

TLadd · 2016-11-28T22:29:15Z

I didn't do anything with atom's node version; I was referring to the node version used in my console to run

react-native run-ios

mithunm93 · 2016-11-28T23:04:06Z

This didn't work for me, I was using node v4.5.0 before, and the same error occurs when i switch to v6.3.0. Could you confirm that the node version is indeed the issue? Thanks for your help

nanandn · 2016-11-29T01:22:17Z

Node v6.3.0 didn't fix the issue for me also.

leochiu-work · 2016-11-29T15:37:24Z

Same here

imnnquy · 2016-12-02T18:55:55Z

+1 Same here

nonameolsson · 2016-12-03T17:13:41Z

I can agree, I have the same issue. First I thought it was something wrong with Node or something else. I have been using Visual Studio Code for a while, but I'm really eager to switch to Atom again.

The app runs without any problems and debugging from VS Code works. I can start the app and edit it with Atom also. But when attaching Nuclide's debugger to the app it wait on connection, just as it should. The problem is when I enable Remote Debug from the iOS emulator. Then the app crashes and the error occurs.

JeffreyVest · 2016-12-03T17:53:08Z

Same. Just getting into React Native. Was following what I thought was the preferred path for editing and was disappointed to find that I can't debug at all due to this issue. I get the getValue(), repeated stack trace like another issue here showed a screen shot of.

sfeese · 2016-12-05T20:25:13Z

+1 same here
different node versions didn't help, I tried 6.3.0, 7.0.0 and 7.2.0

matthewwithanm · 2016-12-07T05:51:52Z

Hey all, we're aware of issues with debugging React Native. We're currently working on debugging using JSC (instead of Node) so we haven't prioritized fixing the node issues. We're hoping to roll that out within the next few releases (before the holidays). Sorry for the pain.

@johnsonsu We actually are using the system node. You can change which node we use via the "Path to Node" setting in the Nuclide settings. You can try changing that to point to an older version.

richardkazuomiller · 2016-12-09T23:23:35Z

@matthewwithanm Which version should we be using?

fifiteen82726 · 2016-12-17T17:11:18Z

The same issue +1

theobouwman · 2016-12-22T19:32:34Z

same issue

theobouwman · 2016-12-22T19:38:35Z

same here

peter-jozsa · 2016-12-23T11:39:35Z

same here

darrenwu · 2016-12-30T03:26:13Z

same here

Liruwei · 2016-12-30T03:32:18Z

same issue

vinas8 · 2017-01-04T07:41:36Z

same issue

macnux · 2017-01-04T19:07:25Z

same issue +1

danbarbarito · 2017-01-05T09:50:46Z

Same issue.....

smkhalsa · 2017-01-05T22:38:54Z

@matthewwithanm any update on this?

glebovitz · 2017-01-07T19:34:43Z

so ... where do we go from here?

dillonykyang · 2017-01-09T17:31:34Z

same issue here.

Mentioum · 2017-01-10T03:11:42Z

same issue.

StephanPartzsch · 2017-01-11T14:00:08Z

same here

wellyshen · 2017-01-25T04:23:40Z

@johnislarry How to upgrade my RN from the master through the "react-native-git-upgrade" command? Or some other appropriate ways?

johnislarry · 2017-01-26T15:37:00Z

@wellyshen If you're on Android, this guide seems helpful: https://facebook.github.io/react-native/docs/android-building-from-source.html

If not, then you could try asking in the RN repo

waterstar · 2017-02-03T14:18:25Z

update your package.json and do a "npm install".
"react-native": "0.42.0-rc.1"

johnislarry · 2017-02-03T19:00:28Z

The release candidate containing the fix is out, if somebody wants to confirm that this issue doesn't repro anymore.

MehmetKaplan · 2017-02-04T07:51:21Z

Sorry but bad news. It did not work for me. I hope it is only related with something I did wrong.

The enviroment and the steps that I did are as follows:

===================================================================

Using Mac OS - Sierra 10.12.3

Dowloaded February 2017 Pre-release from https://github.com/facebook/react-native/releases.
Unzip the file
Entered to the extracted directory
Run "npm install”
mv AwesomeProject/ AwesomeProject_backup
react-native init AwesomeProject
mv ./AwesomeProject_backup/images ./AwesomeProject. (These are my project specific files, you can skipo)
mv AwesomeProject_backup/index.ios.js AwesomeProject/ (My project is only iOS for now, you can also move androidd file as well)
Open Atom
Remove existing AwesomeProject folder inside Atom file tree
Re-add AwesomeProject in Atom’s file tree
Command-shift-p then React Native: Start Packager
Command-shift-p then React Native: Start Debugger
Switch to terminal window, run, "react-native run-ios”

===================================================================

nanandn · 2017-02-04T16:38:35Z

I tried react-native 0.42.0-rc.1. I don't see the "Maximum call stack size exceeded " error. I am able to start the debugger and connect. I can stop at the breakpoints when the application loads.

But after that my app does not work properly. The application renders. But I can't interact with it. The events are not fired. I have an 'onClick' event registered on one of the views. Those events are not fired. At this point all I can do is quit atom and restart.

Just to confirm that there is nothing wrong with my app... I can debug using chrome developer tools and it works fine.

Anand

nanandn · 2017-02-04T17:55:48Z

I used to see the error "Maximum call stack size exceeded " when I debug using intellij. With react-native 0.42.0-rc.1 I don't see that error anymore.

waterstar · 2017-02-06T07:41:48Z

With 0.42.0-rc.1, the problem is fixed for me.

fsjack · 2017-02-09T11:07:19Z

With 0.42.0-rc.1 the "Maximum call stack size exceeded " seem has been fixed, but I got another issue which is that the app is totally freeze when attach to debugger, not only Nuclide but also Chrome debugger as well.

pishty1 · 2017-02-09T12:06:53Z

hello guys, i have downloaded the 0.42.0-rc.1 and did an npm install in the downloaded folder.
react-native -V returns 0.42.0-rc.1,
was wondering what other steps do i need to take.
I changed the react-native's version number in my project's package.json to 0.42.0-rc.1 and did npm install, i get unmet peer dependency for the that version of react native. i know am doing a step wrong somewhere, any help is greatly appreciated. i would love to get the debugger working

update:
here are the new steps am taking now to install 0.42.0-rc.1

download the rn 0.42.0-rc.1 zip file, unzip and run npm install from within the folder
rename the unzipped folder to react-native and move it into the node_modules folder in my project
change the rn version to 0.42.0-rc.1 in the package.json
run npm install from within my project

are these the right steps to take to install 0.42.0-rc.1 ?

vbence86 · 2017-02-13T14:53:39Z

"reach-native": "0.42.0-rc.1" and then npm i fixed the issue for me as well.

itsthejb · 2017-02-20T13:13:28Z

Hi all,

Hmmm, well this is fun. Trying to follow the instructions on https://facebook.github.io/react-native/docs/upgrading.html. The react-native-git-upgrade module didn't work, so I tried the alternative steps. Tried to install all RCs 1-3, but I always get the same equivalent error:

# npm install --save react-native@0.42.0-rc.3
npm WARN deprecated node-uuid@1.4.7: use uuid module instead
mobile@0.0.1 /Users/jcrooke/dev/Onboarding/extaisy
└── UNMET PEER DEPENDENCY react-native@0.42.0-rc.3

npm WARN react-native-navbar@1.6.0 requires a peer of react-native@>= 0.16 but none was installed.

I'm an npm-newbie, but doesn't this mean the module is dependent on itself? 💀

villers · 2017-02-20T15:57:54Z

@vbence86 "react-native": "0.42.0-rc.1"

jmfirth · 2017-02-25T18:25:43Z

Just wanted to leave a report:

Environment

RN: 0.42.0-rc.3
Atom: 1.14.3
Nuclide: 0.207.0
OS: MacOS

Status

Attaches to packager without error
Can hit breakpoints before HMR
Can hit breakpoints after HMR but maps to an empty source file

valeriik · 2017-03-18T06:18:49Z

For some reason I am not able to start debugger. After selection of "Debug JS Remotely" I see "Starting debugger" status only.

Steps to Reproduce

Create a sample app using react-native init.
Start the react native packager in nuclide
Start the debugger in nuclide
Start the application - react-native run-ios
Start Remote JS Debugging from IOS simulator

Environment

Atom version: 1.15.0
Nuclide package version: 0.210.0
React Native version: 0.42.0 / 0.42.0-rc.1 / 0.42.0-rc.3
Platform(s) (iOS, Android, or both?): iOS
Device info Simulator/Device? - Simulator iOS 10.2 / iOS 8.1
OS version? - MacOS 10.12.3
Debug/Release? - Debug
Community Packages (17)

├── atom-beautify@0.29.17
├── atom-react-native-autocomplete@0.0.27
├── atom-react-native-css@1.1.3
├── busy-signal@1.3.0
├── file-icons@2.0.17
├── flow@0.5.3
├── intentions@1.1.2
├── language-babel@2.56.2
├── language-javascript-jsx@0.3.7
├── linter@2.1.0
├── linter-ui-default@1.2.1
├── minimap@4.26.8
├── nuclide@0.210.0
├── react-es6-snippets@0.3.0
├── react-native-snippets@0.3.0
├── react-snippets@0.7.2
└── redux-snippets@0.2.2

Status

Attaches to packager without error
Application works fine
Can successfully see my logs in chrome debugger
But Nuclide debugger did not start

Separate question was created:
https://stackoverflow.com/questions/42807415/nuclide-debugger-does-not-launch-for-react-native

johnsonsu · 2017-03-18T13:39:16Z

@valeriik Try starting the packager by checking the option in the "Start debugging" popup

ajostergaard · 2017-03-18T15:11:33Z

@valeriik did the iOS simulator open a Chrome window for debugging when you started it? If so this will block the port etc etc. You need close that window and try again...

valeriik · 2017-03-30T08:35:31Z

@johnsonsu thanks
@ajostergaard with your hint the situation is changed, debugger went into status "The debugee is currently running." (screenshot) BUT I see in simulator blank white screen only (screenshot). For testing purposes I've also created new blank proj, but nothing changed, I see the same white screen only. When I disable "Remote JS Remotely" I see expected screen with working app (screenshot). Can someone advice? Thanks.

ajostergaard · 2017-03-31T11:01:33Z

@valeriik given that you are not seeing the dreaded "Maximum call stack size exceeded" I suggest creating a new issue as yours is clearly unrelated.

ajostergaard · 2017-03-31T11:03:21Z

@nanandn if I'm not mistake this issue was a React Native issue (something to do with using a different JS engine) and should now be resolved. Is it working for you with the latest RN?

valeriik · 2017-04-01T08:38:20Z

@ajostergaard yes, I am using latest RN ver for now - v0.42.3 (as well as Nuclide v0.214.0 and Atom v1.15.0). I have created separate question regarding the issue with blank white screen using Nuclide debugger. Thanks to all for feedback. I also have a idea to change JS engine in Atom, but fail for now. Maybe someone know how todo it? (so as not to pollute comments on this thread please write your answer on the stackoverflow or on github).

arled · 2017-10-13T10:48:37Z

And who solved it!?

Build100 · 2017-10-24T12:26:34Z

Opened the old project for Android. I see the same error. Fixed in package.json
"react": "16.0.0",
"react-native": "0.49.0",
App working.

mostafaeweda · 2017-11-17T22:58:41Z

This should be fixed with the new RN debugger.

uchilaka · 2017-12-04T09:43:42Z

I'm using react-native 0.50.4 and I'm experiencing this issue. I happen to work across 2 different machines - both Macs, and I'm seeing the same "maximum stack size exceeded" error. That's what led me to this thread.

I should also mention the following:
OS: macOS High Sierra
NPM: 5.5.1
Node: 8.9.1

I've tried the following:

re-installing my node dependencies
using yarn vs. npm directly
using react-native install on a per-package basis

Not sure where the issue is, or if it's a particular dependency that's the culprit, but here are the contents of my package.json:

{
	"name": "{deleted}",
	"version": "{deleted}",
	"private": true,
	"scripts": {
		"start": "node node_modules/react-native/local-cli/cli.js start",
		"test": "jest",
		"postversion": "react-native-version",
		"android": "react-native run-android",
		"ios": "react-native run-ios"
	},
	"dependencies": {
		"b64-to-blob": "^1.2.19",
		"babel-plugin-transform-decorators-legacy": "^1.3.4",
		"firebase": "^4.2.0",
		"firebase-nest": "^0.7.1",
		"google-libphonenumber": "^3.0.4",
		"mobx": "^3.2.2",
		"mobx-firebase-store": "^1.2.1",
		"mobx-react": "^4.2.2",
		"moment-timezone": "^0.5.13",
		"prop-types": "^15.5.10",
		"react": "16.0.0-alpha.12",
		"react-native": "^0.50.4",
		"react-native-camera": "^0.10.0",
		"react-native-elements": "^0.15.0",
		"react-native-fabric": "^0.5.0",
		"react-native-fetch-blob": "^0.10.8",
		"react-native-fs": "^2.5.1",
		"react-native-google-places-autocomplete": "^1.2.12",
		"react-native-google-sign-in": "^0.0.16",
		"react-native-keychain": "^2.0.0-rc",
		"react-native-loading-spinner-overlay": "^0.5.1",
		"react-native-phone-input": "^0.1.8",
		"react-native-swipeout": "^2.2.2",
		"react-native-vector-icons": "^4.4.2",
		"react-native-version": "^2.3.1",
		"react-navigation": "^1.0.0-beta.11",
		"react-redux": "^5.0.6",
		"redux": "^3.7.2",
		"validator": "^8.1.0"
	},
	"devDependencies": {
		"babel-jest": "20.0.3",
		"babel-preset-react-native": "2.1.0",
		"jest": "20.0.4",
		"react-native-tesseract-ocr": "^1.0.8",
		"react-test-renderer": "16.0.0-alpha.12"
	},
	"jest": {
		"preset": "react-native"
	}
}

vlimag · 2017-12-06T23:41:52Z

you are probably setting state on mount or update of component.
Cheers

bottledwalter assigned matthewwithanm Nov 23, 2016

johnislarry mentioned this issue Jan 24, 2017

How to start Debugging React Native Application with Android Studio AVD (Android Virtual Device) #956

Closed

mostafaeweda closed this as completed Nov 17, 2017

radi-cho mentioned this issue May 12, 2018

JavascriptException: Maximum call stack size exceeded when running apk file facebook/react-native#19238

Closed

3 tasks

facebook-github-bot unassigned matthewwithanm Dec 12, 2018

React Native debugging - Maximum call stack size exceeded #900

React Native debugging - Maximum call stack size exceeded #900

Comments

nanandn commented Nov 22, 2016

Issue and Steps to Reproduce

Versions

Additional Details

Marco62 commented Nov 23, 2016

matthieugayon commented Nov 25, 2016

TLadd commented Nov 27, 2016

nanandn commented Nov 27, 2016 • edited Loading

mithunm93 commented Nov 28, 2016

TLadd commented Nov 28, 2016

mithunm93 commented Nov 28, 2016

nanandn commented Nov 29, 2016

leochiu-work commented Nov 29, 2016

imnnquy commented Dec 2, 2016

nonameolsson commented Dec 3, 2016

JeffreyVest commented Dec 3, 2016

sfeese commented Dec 5, 2016

matthewwithanm commented Dec 7, 2016

richardkazuomiller commented Dec 9, 2016

fifiteen82726 commented Dec 17, 2016

theobouwman commented Dec 22, 2016

theobouwman commented Dec 22, 2016

peter-jozsa commented Dec 23, 2016

darrenwu commented Dec 30, 2016

Liruwei commented Dec 30, 2016

vinas8 commented Jan 4, 2017

macnux commented Jan 4, 2017

danbarbarito commented Jan 5, 2017

smkhalsa commented Jan 5, 2017

glebovitz commented Jan 7, 2017

dillonykyang commented Jan 9, 2017

Mentioum commented Jan 10, 2017

StephanPartzsch commented Jan 11, 2017

wellyshen commented Jan 25, 2017 • edited Loading

johnislarry commented Jan 26, 2017

waterstar commented Feb 3, 2017

johnislarry commented Feb 3, 2017

MehmetKaplan commented Feb 4, 2017 • edited Loading

nanandn commented Feb 4, 2017

nanandn commented Feb 4, 2017

waterstar commented Feb 6, 2017

fsjack commented Feb 9, 2017

pishty1 commented Feb 9, 2017 • edited Loading

vbence86 commented Feb 13, 2017 • edited Loading

itsthejb commented Feb 20, 2017

villers commented Feb 20, 2017

jmfirth commented Feb 25, 2017 • edited Loading

valeriik commented Mar 18, 2017 • edited Loading

johnsonsu commented Mar 18, 2017

ajostergaard commented Mar 18, 2017

valeriik commented Mar 30, 2017

ajostergaard commented Mar 31, 2017

ajostergaard commented Mar 31, 2017

valeriik commented Apr 1, 2017 • edited Loading

arled commented Oct 13, 2017

Build100 commented Oct 24, 2017

mostafaeweda commented Nov 17, 2017

uchilaka commented Dec 4, 2017 • edited Loading

vlimag commented Dec 6, 2017 • edited Loading

nanandn commented Nov 27, 2016 •

edited

Loading

wellyshen commented Jan 25, 2017 •

edited

Loading

MehmetKaplan commented Feb 4, 2017 •

edited

Loading

pishty1 commented Feb 9, 2017 •

edited

Loading

vbence86 commented Feb 13, 2017 •

edited

Loading

jmfirth commented Feb 25, 2017 •

edited

Loading

valeriik commented Mar 18, 2017 •

edited

Loading

valeriik commented Apr 1, 2017 •

edited

Loading

uchilaka commented Dec 4, 2017 •

edited

Loading

vlimag commented Dec 6, 2017 •

edited

Loading