Skip to content

Conversation

@QuinnWilton
Copy link

@QuinnWilton QuinnWilton commented Feb 10, 2026

Note that this issue was found while running a static analysis tool I'm working on. It seems like a legitimate finding, but it wasn't an issue I ran into while using Absinthe.

start_deferred_task/1 and start_stream_task/1 used async_nolink without awaiting, leaking a result message and :DOWN message into the caller's mailbox per task. Replace with start_child, which is true fire-and-forget.

start_deferred_task/1 and start_stream_task/1 used async_nolink without
awaiting, leaking a result message and DOWN message into the caller's
mailbox per task. Replace with start_child, which is true fire-and-forget.
@QuinnWilton QuinnWilton changed the title fix leaked async tasks in Incremental.Supervisor fix: leaked async tasks in Incremental.Supervisor Feb 10, 2026
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.

1 participant