Skip to content
This repository has been archived by the owner on Dec 3, 2023. It is now read-only.

Error: stdout maxBuffer exceeded #173

Closed
ghost opened this issue Oct 27, 2017 · 3 comments
Closed

Error: stdout maxBuffer exceeded #173

ghost opened this issue Oct 27, 2017 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 27, 2017

Each time i try to console.log a .getInfo i get this error:
{ Error: stdout maxBuffer exceeded
at Socket.onChildStdout (child_process.js:323:14)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at addChunk (_stream_readable.js:252:12)
at readableAddChunk (_stream_readable.js:235:13)
at Socket.Readable.push (_stream_readable.js:197:10)
at Pipe.onread (net.js:589:20)
cmd: '/root/node_modules/youtube-dl/bin/youtube-dl --dump-json -f best --no-warnings --force-ipv4 ytsearch: rockstar post malone' }

@KarboniteKream
Copy link

KarboniteKream commented Oct 29, 2017

See #126 and #128.

@DuBistKomisch
Copy link

This could be fixed by using spawn instead of exec and buffering the output internally, instead of making everyone use a workaround.

@Kikobeats
Copy link
Collaborator

I'm happy to address this error.

I feel that using execa should be enough, it has sensible good defaults.

What do you think?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants