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.

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

Issue on iphone with atomic-waker #2780

Open
serzhiio opened this issue Oct 11, 2023 · 2 comments
Open

Issue on iphone with atomic-waker #2780

serzhiio opened this issue Oct 11, 2023 · 2 comments
Labels
A-task Area: futures::task needs-mcve Call for participation: This issue needs a Minimal Complete and Verifiable Example

Comments

@serzhiio
Copy link

Caught it recently
IMG_5068

@taiki-e
Copy link
Member

taiki-e commented Oct 15, 2023

Thanks for the report. It seems that this debug assertion is triggered.

// There is a concurrent thread currently updating the
// associated task.
//
// Nothing more to do as the `WAKING` bit has been set. It
// doesn't matter if there are concurrent registering threads or
// not.
//
debug_assert!(
state == REGISTERING || state == REGISTERING | WAKING || state == WAKING
);

Is it possible to provide code to reproduce this?

Also, does the code seem to be running on WASM, not directly on iphone?

@taiki-e taiki-e added the A-task Area: futures::task label Oct 15, 2023
@serzhiio
Copy link
Author

This is from WASM app, unfortunately i can't provide code to reproduce this error.

@taiki-e taiki-e added the needs-mcve Call for participation: This issue needs a Minimal Complete and Verifiable Example label Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-task Area: futures::task needs-mcve Call for participation: This issue needs a Minimal Complete and Verifiable Example
Projects
None yet
Development

No branches or pull requests

2 participants