Skip to content

stdout maxBuffer exceeded #3615

Closed
Closed

Description

@chaiyuxin

OS?

Mac OSX (Yosemite)

Versions.

angular-cli: 1.0.0-beta.22-1
node: 5.3.0

Repro steps.

New project just trying to push and test

The log given by the failure.

stdout maxBuffer exceeded
Error: stdout maxBuffer exceeded
at Socket. (child_process.js:266:14)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Socket.Readable.push (_stream_readable.js:110:10)
at Pipe.onread (net.js:523:20)

Mention any other details that might be useful.

After a ng github-pages:deploy, the build succeed but can't upload it due to that error, i've been trying on multiple repo i get the same error and the project have just been created, nothing custom.

Do you guys had this error ? Any solution ?

Thanks ! :)

Activity

  1. C-4PO commented on Dec 27, 2016

    @C-4PO

    Yea same here! I have absolutely no idea whats going on!

  2. filipesilva commented on Dec 30, 2016

    @filipesilva
    Contributor

    Never see that error myself. Does this happen with a brand new project? Does it only happen on big projects?

  3. petermezei commented on Jan 15, 2017

    @petermezei

    I have the same issue. Here is my repro: https://github.com/petermezei/angular2-cli

  4. petermezei commented on Jan 15, 2017

    @petermezei

    My project is just an init project.

  5. donvadicastro commented on Jan 15, 2017

    @donvadicastro

    Did you found hove to overcome this?

  6. petermezei commented on Jan 16, 2017

    @petermezei

    Hi guys, I found where this issue might come:
    Node mayBuffer size for child_process is too small. Once I wrote my own git commands using node simple-git I got the same error. When I set my mayBuffer value to 500kb it works smoothly.

    So somewhere you should set the maxBuffer size higher in the process.

  7. filipesilva commented on Feb 3, 2017

    @filipesilva
    Contributor

    Closed via #4385.

  8. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  9. locked and limited conversation to collaborators on Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs: repro stepsWe cannot reproduce the issue with the information given

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions