wit-bindgen-go hangs on deeply nested result types

Open
#410 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, wasm
Domain
tooling

Research direction

Start by running the provided go run ./cmd/wit-bindgen-go generate command with poc.wit under the stated memory cap, then inspect the cmd/wit-bindgen-go entry point and the generation path it invokes. Done means the deeply nested WIT package completes and writes generated Go bindings without spinning or being killed.

Written by the indexing model from the issue text.

Description

Summary

wit-bindgen-go generate hangs and is eventually killed (SIGTERM) when processing a legal WIT package that contains a very deeply nested result<_, result<_, list<...>>> shape.

Steps-To-Reproduce

ulimit -Sv 4194304 # 4GB virtual mem cap
go run ./cmd/wit-bindgen-go \
  generate \
  --versioned \
  --generate-wit \
  --out .poc_out \
  poc.wit

poc.wit (validated by wasm-tools component wit)

package x:name5;

interface name1 {
}

interface name2 {
}

interface name3 {
}

interface name4 {
}

interface name5 {
}

interface name6 {
}

interface name7 {
}

interface name8 {
}

interface name9 {
}

world name {
  import name2:name3/x@1.1.0+1.2.0;
  use name2:name3/x@1.1.0+1.2.0.{name5 as name};

  type name2 = tuple<list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, bool>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, bool, bool, bool, bool, bool>;

  type name3 = result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, u32>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>;

  flags name4 {
    name5,
    name6,
    name7,
    name8,
    name9,
    name10,
    name11,
    name12,
    name13,
  }

  type name14 = tuple<list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, bool>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, bool, bool, bool, bool, bool>;

  record name15 {
    name16: bool,
  }

  export name2:name3/x@1.1.0+1.2.0;
}
package name2:name3@1.1.0+1.2.0 {
  interface x {
    type name8 = result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, u32>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>;

    enum name12 {
      name13,
      name14,
    }

    type name10 = result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<f32>>>>>>>>>>>>>>>>>>>>>>>>>>>>;

    type name3 = result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<result<char, result<f32>>>>>>>>>>>>>>>>>>>>>>>>>>>>;

    enum name5 {
      name6,
      name7,
    }

    name2: func(name: result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, u32>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, name1: bool, name2: bool, name3: bool);

    name: async func(name: tuple<f32, tuple<result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<bool>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, bool>>) -> tuple<result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, u32>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, bool>;

    name9: func(name: result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, list<result<_, result<_, u32>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>, name1: bool, name2: bool, name3: bool);

    x11: func();

    x: func();
  }
}

Expected

writes generated Go bindings successfully.

Actual

process spins until killed (OOM).

Environment

ubuntu 22.04, x86-64, Go 1.24.3

Dominant language
Go
Stars
148
Forks
20
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/go-modules

All issues in bytecodealliance/go-modules

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.