Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

timeout_after memory usage #890

Open
smmoosavi opened this issue Feb 20, 2024 · 1 comment
Open

timeout_after memory usage #890

smmoosavi opened this issue Feb 20, 2024 · 1 comment

Comments

@smmoosavi
Copy link

smmoosavi commented Feb 20, 2024 •
edited
Loading

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

It may related to the rust-96084 issue

you can find the example repo here

Environment

RTIC: { version = "2.0.1", features = ["thumbv6-backend"] }
rustc 1.78.0-nightly (d44e3b95c 2024-02-09)
@AfoHT
Copy link
Contributor

AfoHT commented Mar 6, 2024

Thank you for reporting! I forgot to make a note here during the meeting

Discussed during meeting: hackmd

Matrix: message

dalegaard added a commit to dalegaard/rtic that referenced this issue Mar 26, 2024
@dalegaard
Change timeout/delay functions to non-async
96f99df 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes rtic-rs#890.
@dalegaard dalegaard mentioned this issue Mar 26, 2024
Merged
dalegaard added a commit to dalegaard/rtic that referenced this issue Mar 26, 2024
@dalegaard
Change timeout/delay functions to non-async
99e69d1 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes rtic-rs#890.
dalegaard added a commit to dalegaard/rtic that referenced this issue Jun 20, 2024
@dalegaard
Change timeout/delay functions to non-async
2a18277 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes rtic-rs#890.
dalegaard added a commit to dalegaard/rtic that referenced this issue Jun 23, 2024
@dalegaard
Change timeout/delay functions to non-async
38f519f 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes rtic-rs#890.
dalegaard added a commit to dalegaard/rtic that referenced this issue Jun 23, 2024
@dalegaard
Change timeout/delay functions to non-async
390a8ca 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes rtic-rs#890.
github-merge-queue bot pushed a commit that referenced this issue Aug 21, 2024
@dalegaard @korken89
Change timeout/delay functions to non-async (#910)
a636f4e 
Because of a compiler bug, the `async` implementations of
`delay`/`delay_until`/`timeout`/`timeout_at` produce much larger RAM
footprint than they should.

Fixes #890.

Co-authored-by: Emil Fresk <emil.fresk@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smmoosavi @AfoHT