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

Wasm GC: assertion failed: types.is_subtype(actual_ty, expected_ty) #10376

Closed
fitzgen opened this issue Mar 11, 2025 · 2 comments
Closed

Wasm GC: assertion failed: types.is_subtype(actual_ty, expected_ty) #10376

fitzgen opened this issue Mar 11, 2025 · 2 comments

Comments

@fitzgen
Copy link
Member

fitzgen commented Mar 11, 2025

The second one is the case with the serialization. It fails even in the standalone version of Wasmtime with assertion failed: types.is_subtype(actual_ty, expected_ty) error.

assertion_failed__types_is_subtype.wasm.zip

Originally posted by @epsylonix in #9714

@fitzgen
Copy link
Member Author

fitzgen commented Mar 12, 2025

What would really help with diagnosing and fixing this bug is a test case reduction. Hard to figure out what is going on with a 235KiB test case.

FWIW, we have some docs on using wasm-shrink to reduce test cases here, although we would probably want to use creduce on the .wat disassembly of this .wasm instead, since wasm-shrink doesn't have Wasm GC support yet.

@fitzgen
Copy link
Member Author

fitzgen commented Mar 12, 2025

This is passing on main, at least as of 5b9e87650.

Going to go ahead and close this, but please open a new issue if you find anything else, @epsylonix!

@fitzgen fitzgen closed this as completed Mar 12, 2025
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

1 participant