Skip to content

Future.after can lead to stack overflow errors with completed futures #28

@iconara

Description

@iconara

When lots of futures are given to Future.after you can get a stack overflow error since each callback registers as a callback to the next future, and the call stack grows and grows as long as they are already resolved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions