You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2024. It is now read-only.
Using the @defer directive when returning an array of async functions causes helix to go into an infinite loop and crash. This happens when the request is cancelled before all async resolvers have returned. I have isolated the problem to this for await loop in process-request.ts. It probably has something to do with the async iterator not stopping correctly (see this comment on the async iterator proposal).
Here is a minimal project which reproduces the issue. (Reproduced with 16.1.0-experimental-stream-defer.6)
In GraphQLi starting and stoping this query before the timeout has completed causes the application to increase memory usage until it crashes with JavaScript heap out of memory.
Using the
@defer
directive when returning an array of async functions causes helix to go into an infinite loop and crash. This happens when the request is cancelled before all async resolvers have returned. I have isolated the problem to thisfor await
loop inprocess-request.ts
. It probably has something to do with the async iterator not stopping correctly (see this comment on the async iterator proposal).Here is a minimal project which reproduces the issue. (Reproduced with
16.1.0-experimental-stream-defer.6
)In GraphQLi starting and stoping this query before the timeout has completed causes the application to increase memory usage until it crashes with
JavaScript heap out of memory
.The text was updated successfully, but these errors were encountered: