wasmtime / PR #12362 Handle OOM in `Engine::new` · git-wasmtime

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing", "wasmtime:api", "wasmtime:config"

Thus the following users have been cc'd because of the following labels:

fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (Jan 16 2026 at 01:06):

github-actions[bot] commented on PR #12362:

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

[ ] If you added a new Config method, you wrote extensive documentation for
it.

<details>

Our documentation should be of the following form:

```text
Short, simple summary sentence.

More details. These details can be multiple paragraphs. There should be
information about not just the method, but its parameters and results as
well.

Is this method fallible? If so, when can it return an error?

Can this method panic? If so, when does it panic?

Example

Optional example here.
```

</details>

[ ] If you added a new Config method, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.

<details>

For example, if you expose a new strategy for allocating the next instance
slot inside the pooling allocator, you should ensure that at least one of our
fuzz targets exercises that new strategy.

Often, all that is required of you is to ensure that there is a knob for this
configuration option in [wasmtime_fuzzing::Config][fuzzing-config] (or one
of its nested structs).

Rarely, this may require authoring a new fuzz target to specifically test this
configuration. See [our docs on fuzzing][fuzzing-docs] for more details.

</details>

[ ] If you are enabling a configuration option by default, make sure that it
has been fuzzed for at least two weeks before turning it on by default.

[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html

<details>

To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.

To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.

Learn more.

</details>

Wasmtime GitHub notifications bot (Jan 20 2026 at 21:10):

fitzgen updated PR #12362.

Wasmtime GitHub notifications bot (Jan 20 2026 at 21:56):

fitzgen updated PR #12362.

Wasmtime GitHub notifications bot (Jan 21 2026 at 14:57):

alexcrichton submitted PR review.

Wasmtime GitHub notifications bot (Jan 21 2026 at 18:45):

fitzgen added PR #12362 Handle OOM in Engine::new to the merge queue

Wasmtime GitHub notifications bot (Jan 21 2026 at 19:05):

github-merge-queue[bot] removed PR #12362 Handle OOM in Engine::new from the merge queue

Wasmtime GitHub notifications bot (Jan 21 2026 at 19:23):

fitzgen updated PR #12362.

Wasmtime GitHub notifications bot (Jan 21 2026 at 19:23):

fitzgen has enabled auto merge for PR #12362.

Wasmtime GitHub notifications bot (Jan 21 2026 at 19:36):

fitzgen added PR #12362 Handle OOM in Engine::new to the merge queue

Wasmtime GitHub notifications bot (Jan 21 2026 at 20:01):

fitzgen merged PR #12362.

Wasmtime GitHub notifications bot (Jan 21 2026 at 20:01):

fitzgen removed PR #12362 Handle OOM in Engine::new from the merge queue

Last updated: Jan 29 2026 at 13:25 UTC