-
Notifications
You must be signed in to change notification settings - Fork 61
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
ongoing fetch will cause cpu 100% #145
Comments
Although I have tried to fix this issue many times, it still has not been resolved. The underlying reason is that during the wasi poll, I continuously receive a writable status, but what I actually expect is a readable status. I thought I had fixed it before, but it seems that’s not the case. I will keep trying. |
WasmEdge/wasmedge_hyper_demo#11 I found a similar problem. And I traverse wasmedge-quickjs code, the code call wasi poll through wasi_tokio? |
I use example here https://github.com/WasmEdge/wasmedge_reqwest_demo same behavior... sad, nothing about wasmedge-quickjs |
We found that this issue is caused by an incorrect implementation of wasi_poll in the WasmEdge runtime on macOS. The WasmEdge runtime is being fixed. |
run code below in MacOS arm64. build wasmedge-quickjs from latest main branch, and use wasmedge 0.14.1
during the fetch progress, seems there is a infinity loop
The text was updated successfully, but these errors were encountered: