Skip to content

Stack overflow if high water mark is too high #2

@Twipped

Description

@Twipped

Since the lib uses recursion to pull down and fill itself up, I'm running into problems with hitting the top of the call stack when using a high water mark over, say, 4000. I didn't investigate too deeply into what the limit was.

An option to have it invoke read via setImmediate every N iterations could solve this without much performance penalty.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions