Skip to content

Fix ERR_CHILD_PROCESS_STDIO_MAXBUFFER#41

Open
Lambdac0re wants to merge 1 commit intozapolnoch:masterfrom
Lambdac0re:patch-1
Open

Fix ERR_CHILD_PROCESS_STDIO_MAXBUFFER#41
Lambdac0re wants to merge 1 commit intozapolnoch:masterfrom
Lambdac0re:patch-1

Conversation

@Lambdac0re
Copy link

The followin error occurs, when tesseract produces more stderr output than the default nodejs maxBuffer.

uncaughtException RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stderr maxBuffer length exceeded

Here I just increase the value by 4x the default and tesseract runs fine again.

The followin error occurs, when tesseract produces more stderr output than the default nodejs maxBuffer.

uncaughtException RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stderr maxBuffer length exceeded

Here I just increase the value by 4x the default and tesseract runs fine again.
@EHadoux
Copy link

EHadoux commented Sep 29, 2022

Yeah, I need that as well especially with hocr that is quite chatty. However, perhaps making it customisable would be better than a fixed value.
Also, wider point, it's probably better to use spawn rather than exec, see https://www.hacksparrow.com/nodejs/difference-between-spawn-and-exec-of-node-js-child-rocess.html for instance.

@Lambdac0re
Copy link
Author

That is true, but let's start with this first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants