[Ask] recursive process. nexttick detected. This will break in the next version of node. Please use setimmediate for Recursive deferral.

1. On Friday, the node. js TCP persistent connection Server framework was tested and everything started to be more common (no special problem ).

2. Suddenly, the client group used for stress testing was closed.

3. At this time, the node. js server reported "caught exception: Error: Read econnreset ".

4. I have seen this before when I used it as a Linux Server (ignore it)SIGPIPESignal, nodejs does the same by default.

5. But then an error occurs in the title. I think this is definitely not the reason for direct calling.

6. I want to write a simple server, link the server, do not receive or send packets, and close the pressure test client group together. See what it looks like.

7. still appear

Caught exception: Error: Read econnreset
At errnoexception (net. JS: 904: 11)
At TCP. onread (net. JS: 558: 19) ...... (several)
(Node) Warning: recursive process. nexttick detected. This will break in the next version of node. Please use setimmediate for Recursive deferral ...... (several items)
Node. JS: 0 // copyright joyent, Inc. And other node contributors.
^
Rangeerror: Maximum call stack size exceeded 8. I think this is definitely not a problem for me or nodejs itself. It may be a problem that has not been set. (Isn't the number of Linux Process handles 1024 by default! You must use ulimit-N ). 9. I started to look at the official node. js documentation here. It was an API call (a bit violent, but at first I thought it should be a global setting problem, so it starts from process, so we can see this in a few minutes )! 10. I tried to change it and it immediately took effect. 11. But the heart is still some not steadfast, I am afraid I still have to wait to deal with the cocos2d-x after the problem has time, and then look at nodejs this piece of source code. Process. maxtickdepth

• Number default = 1000

Callbacks passedprocess.nextTickWillUsuallyBe called at the end of the current flow of execution, and are thus approximately as fast as calling a function synchronously. left unchecked, this wowould starve the event loop, preventing any I/O from occurring.