MA3CIN added the bug label to Issue #10482.
MA3CIN opened issue #10482:
I'm having trouble with increasing the allowed table elements per table in the pooling allocator - i'm hitting the hard limit of 20k

Test Case
Too big of a wasm file to upload here.... (32Mb), it is accessible here: https://github.com/MA3CIN/wasmtime-error/blob/main/wasm-server.wasm
Steps to Reproduce
Run the wasm file with wastime server: "wasmtime serve wasm-server.wasm"
Expected Results
I expected the allowed table elements per table in the pooling allocator limit to be increased when using the -W max-table-elements cli arguments
Actual Results
I'm still hitting the limit

Versions and Environment
Wasmtime version or commit: wasmtime 31.0.0 (7a9be587f 2025-03-20)
Operating system: Ubuntu 22.04.3 LTS
Architecture: N/A, single wasm instance
Extra Info
Works fine when i run it with wasmtime run, i only hit the limit with wasmtime serve..
Maybe a similar problem to https://github.com/bytecodealliance/wasmtime/issues/8504
alexcrichton commented on issue #10482:
Thanks! This is a bad interaction between the deafults of
wasmtime serve
which is to use the pooling allocator and the error messages here. You can fix this locally by setting-O pooling-table-elements=N
. Additionally https://github.com/bytecodealliance/wasmtime/pull/10483 should fix this issue too.
alexcrichton closed issue #10482:
I'm having trouble with increasing the allowed table elements per table in the pooling allocator - i'm hitting the hard limit of 20k

Test Case
Too big of a wasm file to upload here.... (32Mb), it is accessible here: https://github.com/MA3CIN/wasmtime-error/blob/main/wasm-server.wasm
Steps to Reproduce
Run the wasm file with wastime server: "wasmtime serve wasm-server.wasm"
Expected Results
I expected the allowed table elements per table in the pooling allocator limit to be increased when using the -W max-table-elements cli arguments
Actual Results
I'm still hitting the limit

Versions and Environment
Wasmtime version or commit: wasmtime 31.0.0 (7a9be587f 2025-03-20)
Operating system: Ubuntu 22.04.3 LTS
Architecture: N/A, single wasm instance
Extra Info
Works fine when i run it with wasmtime run, i only hit the limit with wasmtime serve..
Maybe a similar problem to https://github.com/bytecodealliance/wasmtime/issues/8504
MA3CIN commented on issue #10482:
Thanks for the quick reaction @alexcrichton, I appreciate your help :)
Last updated: Apr 18 2025 at 07:03 UTC