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 1, 2021. It is now read-only.
Inspecting the data map over multiple requests with the koa example reveals that the map is always growing in size, not just in keys, but the data is left lying around too. This will lead to larger and larger memory use over time, despite those continuations being finished. Is there anything that can be done about this? Using remove doesn't make the problem go away.
I'm guessing that since it's not possible to know if async functions have finished with the storage yet that we're forced to leave it lying around?
The text was updated successfully, but these errors were encountered:
Inspecting the data map over multiple requests with the koa example reveals that the map is always growing in size, not just in keys, but the data is left lying around too. This will lead to larger and larger memory use over time, despite those continuations being finished. Is there anything that can be done about this? Using
remove
doesn't make the problem go away.I'm guessing that since it's not possible to know if async functions have finished with the storage yet that we're forced to leave it lying around?
The text was updated successfully, but these errors were encountered: