Programs that succeed to execute with v1.6.0 sometimes hang indefinitely with v1.8.1 during instantiation.

[davidmdm]

Describe the bug Programs that succeed to execute with v1.6.0 sometimes hang indefinitely with v1.8.1 during instantiation. The same program crashes with v1.7.x

To Reproduce Clone the example repository:

git clone https://github.com/davidmdm/wzbug.git
cd ./wzbug
./test.sh

Expected behavior Program should behave the same as with the v1.6.0 runtime.

Environment (please complete the relevant information):

• Go version: 1.23.3
• wazero Version: v1.8.1
• Host architecture: Arm64 (M2 Mac)
• Runtime mode: Compiler

Additional context

Incredibly rare and difficult to reproduce. If I tweak the example program slightly, the bug disappears. If I don't use stdin the bug disappears. However I don't want to write programs fearing that the perfect storm will hang my execution.

[evacchi]

If I don't use stdin the bug disappears.

that's really useful, I wonder if that bug lies there entirely 🤔 stdin has a special treatment, especially in poll_oneoff, and when used interactively

[mathetake]

relevant to https://github.com/tetratelabs/wazero/issues/2178 ?

[davidmdm]

@evacchi here is an incomplete list of weird things which have made the program succeed.

• using json.Unmarshal instead of K8s/yaml Decoder
• hard coding the data instead of parsing it from stdin
• parsing the data as is but removing any further code related to json encoding of the various k8 APIs

However if I parse stdin using the yaml decoder from k8s and use that data it hangs.