Codex VSCode extension on Windows stalls and crashes on v. 0.4.51

[ysmartin]

What version of Codex is running?

0.4.51

What subscription do you have?

Plus

Which model were you using?

GPT-5.1-Codex-Max

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

This error appears on the Codex chat view.

An error has occurred
Codex crashed with the following error:

Codex process errored: Codex process is not available
thread 'tokio-runtime-worker' panicked at core\src\util.rs:21:9:
Function call output is missing for call id: call_Mx1hEL51XPh0uQKthJIcbenN
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Some things to try:

Check your config.toml for invalid settings
Check your settings to disable running in WSL if you are seeing compatibility issues
Try downloading a different version of the extension
Click reload to restart the Codex extension, or visit our documentation for additional help.

Open Config.toml
Reload

What steps can reproduce the bug?

Open Codex chat Window. Click on a previous conversation. The chat view opens, it keeps trying to load the conversation, and after a while, the error above appears.

What is the expected behavior?

No response

Additional information

Same results on a portable installation of VSCode.
The error disappears on WSL mode (but the list of chats in chat history is different).

[etraut-openai]

Thanks for reporting the problem. I suspect it has something to do with one or more of your saved session files.

It would be really useful to have a full stack crawl. You can get that by setting the RUST_BACKTRACE environment variable to 1 before launching your IDE. Then trigger the crash.

We may also be able to get some additional information from your log files. Trigger the crash, then reload the extension and create a new conversation. Submit a dummy prompt like "Hi". This will allocate a session (thread) ID that we can use for tracking purposes. Then use the /feedback slash command to upload your logs and paste the thread ID here. I can then look at your logs to see if there's a stack crawl. I don't know if the crash will be logged and flushed prior to the process being terminated.