-
Notifications
You must be signed in to change notification settings - Fork 30k
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
The max length of console.log output is 8275 #9546
Comments
Can't reproduce on Windows 7 x64 with cmd or Powershell. |
var testString = Array(8276).join('a');
console.log('length = ' + testString.length);
console.log(testString);
console.log('finished'); Use the codes above, the second Change to |
Can't reproduce as well. |
Start Node.js command prompt, and execute the following command: D:\>node -p "process.stdout.write(util.format.apply(null, [Array(8278).join('a')]))" Nothing output, but if you change the array size to |
For me, it does print all the string even with |
Irrelevant: |
Can confirm the same blank output on my machine.
|
Does anything change if you wait for some time before exiting? E.g. do a |
Repro'd. As the OP said this appears in 7.1.0. I bet it was the libuv 1.10.0 upgrade... Unfortunately I am unable to bisect on Windows so... @saghul, @cjihrig, @bnoordhuis Edit: Adding a timeout does not help, probably not related to #6456. |
Does it work with the patch from issue#9542? |
I'm having the same problem on both Windows 10 build 14965 and Windows Server 2016. My app suddenly exited without displaying any error message, at where a very long string should be console.log'd, after upgraded node to 7.1.0. @Fishrock123 @killroy42 I took some time to do the bisect and tested out the patch, libuv 1.10.0 upgrade IS the cause of the problem and the patch FIXES it. |
Closing. #9542 closed via libuv/libuv@d0c2641. Please reopen if that is not correct. |
Fixes: nodejs#9542 Fixes: nodejs#9546 PR-URL: nodejs#9647 Reviewed-By: Imran Iqbal <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Fixes: #9542 Fixes: #9546 PR-URL: #9647 Reviewed-By: Imran Iqbal <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Fixes: #9542 Fixes: #9546 PR-URL: #9647 Reviewed-By: Imran Iqbal <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Fixes: #9542 Fixes: #9546 PR-URL: #9647 Reviewed-By: Imran Iqbal <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Fixes: nodejs/node#9542 Fixes: nodejs/node#9546 PR-URL: nodejs/node#9647 Reviewed-By: Imran Iqbal <[email protected]> Reviewed-By: Santiago Gimeno <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
Using the following codes, the second
console.log
will be failed without any error message and the program exits; but it worked on 7.0.0.Reduce the array size to 8276, the program works as expected.
The text was updated successfully, but these errors were encountered: