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
I investigated the memory usage of the timeout_after function. The returned future size is larger than expected. If a future with the size of n is passed into the timeout_after function, the returned future will have the size of n * 4 + 120
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.
Fixesrtic-rs#890.
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.
Fixesrtic-rs#890.
I investigated the memory usage of the
timeout_after
function. The returned future size is larger than expected. If a future with the size ofn
is passed into thetimeout_after
function, the returned future will have the size ofn * 4 + 120
It may related to the rust-96084 issue
you can find the example repo here
Environment
The text was updated successfully, but these errors were encountered: