• Corngood@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    8 months ago

    I feel like node’s async model makes it really easy to cause a bug like this, and really difficult to track it down.

    It was left to the OS to catch the leak, because the program was written in such a way that it was able to run a gazillion of these tasks concurrently.