Skip to content

Codex desktop app crashes on Windows x64 after Codex Micro / serialport path is triggered #33505

Description

@giarld

Summary

Codex desktop app on Windows x64 crashes when switching/opening conversations. This appears to match #33409 / the serialport.node / Codex Micro gate issue.

No dump is attached because full process dumps may contain sensitive memory. Below is the WinDbg stack summary only.

Environment

  • OS: Windows x64, build shown in dump as 10.0.26100.1
  • App package: OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0
  • Process: ChatGPT.exe
  • App process version in dump: 150.0.7871.115
  • System Node after upgrade: v26.4.0 / npm 11.17.0

Timeline / behavior

  • The app was updated yesterday.
  • Crashes started today when switching/opening conversations.
  • I later uninstalled and reinstalled the app today, so the current package install timestamp only reflects the reinstall, not the original update time.
  • Reinstalling did not fix the issue.
  • Upgrading the system Node.js did not fix the issue.
  • Fresh crash dumps after reinstall still show the same failure in the bundled native module.

WinDbg evidence

Exception:

ExceptionCode: c06d007f
ERROR_CODE: (NTSTATUS) 0xc06d007f
Failure bucket: APPLICATION_FAULT_c06d007f_serialport.node!Unknown
Faulting module: serialport.node

Faulting module path:

C:\Program Files\WindowsApps\OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0\app\resources\app.asar.unpacked\node_modules\@worklouder\device-kit-oai\node_modules\@worklouder\wl-device-kit\node_modules\serialport\node_modules\@serialport\bindings-cpp\build\Release\serialport.node

Module metadata:

Image name: serialport.node
Timestamp: Sat Jul 22 19:57:37 2023 (64BBC431)
ImageSize: 0003E000

Earlier dump analysis also showed the loader failure as missing export:

node.exe!napi_module_register
Win32 error 127 / ERROR_PROC_NOT_FOUND

Relevant stack excerpt:

KernelBase!RaiseException+0x8a
serialport+0x26430
serialport+0xda95
serialport+0x1aba5
serialport+0xe51e
serialport+0xe694
ntdll!LdrpCallInitRoutineInternal+0x22
ntdll!LdrpCallInitRoutine+0x93
ntdll!LdrpInitializeNode+0x19c
ntdll!LdrpInitializeGraphRecurse+0x6a
ntdll!LdrpPrepareModuleForExecution+0xef
ntdll!LdrpLoadDllInternal+0x284
ntdll!LdrpLoadDll+0x100
ntdll!LdrLoadDll+0x170
KernelBase!LoadLibraryExW+0xff
chrome!uv_dlopen+0xe0
chrome!node::binding::get_linked_module+0x2b65
chrome!node::SetCppgcReference+0xc732
chrome!node_module_register+0x9cc

Current assessment

This does not look like a broken local install, system Node.js issue, node_repl MCP issue, or missing Windows runtime dependency. It looks like the app package contains an old native serialport.node that is incompatible with the Electron/Node runtime path that gets activated by the Codex Micro / Work Louder integration.

A server-side feature flag / Statsig gate activation may explain why the app update happened earlier but the crash started later.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions