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

Function: proxy_on_log failed: Uncaught RangeError: Maximum call stack size exceeded #228

Open
LugiaChang opened this issue Mar 19, 2024 · 5 comments

Comments

@LugiaChang
Copy link

I am injecting a wasm plugin for envoy in the istio 1.18 environment. During the stress test, the following error occurred. I didn't implement on_log in my wasm code, and there are no other recursive calls. I am very confused about the reason for this error.

error envoy wasm external/envoy/source/extensions/common/wasm/wasm_vm.cc:38   Function: proxy_on_log failed: Uncaught RangeError: Maximum call stack size exceeded    thread=87

When this error occurs, it seems that the thread will continuously display the "wasm_fail_stream" error, and the request will return a 503 response.

POST /infopb.InfoService/Upsert HTTP/2" 200 - wasm_fail_stream - "-" 1257 0 1167 - "-" "grpc-go/1.59.0" "698b416f-e3ee-4f8e-b579-d563d7c37b59" "infosvr-mesh:5000" "11.166.153.22:5000" outbound|5000||infosvr.perf-master.svc.cluster.local 11.166.149.157:47728 11.166.160.143:5000 11.166.149.157:51304 - main
@kyessenov
Copy link

CC @PiotrSikora

@cage1993
Copy link

cage1993 commented Sep 5, 2024

Same problem

@pi-pi-miao
Copy link

you can use https://github.com/pi-pi-miao/proxy-wasm-rust-sdk solve the problem

@pi-pi-miao
Copy link

the panic may be It happens elsewhere

@LugiaChang
Copy link
Author

the panic may be It happens elsewhere

It may be wasm runtime error. see istio/istio#49972

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants