Codex Desktop freezes when pasting certain error logs into a new chat

Codex Desktop freezes when pasting certain error logs into a new chat, so this does not appear to be only a large-session or session-restore issue.

Environment

• Platform: Windows
• Codex App version: 26.601.2237.0
• App: Codex Desktop
• Scenario: Pasting debugging error logs directly into a new chat input

What happens

Codex Desktop can freeze or become unresponsive immediately after I paste certain error logs into the chat.

This also happens in a new chat, not only when reopening an existing session. So the issue does not seem to be caused only by large persisted session history or automatic session restoration.

At first I suspected that message length might be involved, but I am no longer sure. Some logs that are not extremely long can still trigger the freeze.

Examples of logs that triggered the freeze

Example 1: Python / PyTorch traceback

INFO:guyon_113_v2pro:Train Epoch: 4 [57%]
INFO:guyon_113_v2pro:[3.770758867263794, 2.899627208709717, 15.167693138122559, 20.37558937072754, 0.0, 1.9120768308639526, 700, 9.995000937421877e-05]

Traceback (most recent call last):
  File "...\\GPT_SoVITS\\s2_train.py", line 684, in <module>
  File "...\\torch\\multiprocessing\\spawn.py", line 215, in join
    raise ProcessRaisedException(msg, error_index, failed_process.pid)

torch.multiprocessing.spawn.ProcessRaisedException:

RuntimeError: The size of tensor a (282) must match the size of tensor b (218) at non-singleton dimension 2

subprocess.CalledProcessError: Command '[...\\runtime\\python.exe', '-s', 'GPT_SoVITS/s2_train.py', '--config', '...\\TEMP\\tmp_s2_guyon_113_v2pro.json']' returned non-zero exit status 1.

Example 2: n8n / ComfyUI JSON error with stackTrace

{
  "errorMessage": "'bool' object is not callable [line 21]",
  "errorDescription": "5420 (SamplerCustomAdvanced)",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "2.21.7 (Self Hosted)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "Error: ComfyUI prompt failed at node 5431:5420 (SamplerCustomAdvanced): 'bool' object is not callable",
      "",
      "    at VmCodeWrapper (evalmachine.<anonymous>:21:9)",
      "    at evalmachine.<anonymous>:86:2",
      "    at Script.runInContext (node:vm:149:12)",
      "    at runInContext (node:vm:301:6)",
      "    at result (D:\\\\code\\\\pixi\\\\n8n\\\\node_modules\\\\@n8n\\\\task-runner\\\\dist\\\\js-task-runner\\\\js-task-runner.js:215:61)",
      "    at new Promise (<anonymous>)",
      "    at JsTaskRunner.runForAllItems (D:\\\\code\\\\pixi\\\\n8n\\\\node_modules\\\\@n8n\\\\task-runner\\\\dist\\\\js-task-runner\\\\js-task-runner.js:208:34)"
    ]
  }
}

Important detail

This can happen even in a new chat.

That makes me think the issue may be related to one of these areas:

• paste handling
• markdown/code-block rendering
• syntax highlighting
• stack trace parsing/rendering
• escaped Windows paths
• JSON objects containing stackTrace arrays
• terminal-style traceback text

Expected behavior

Codex should remain responsive when users paste debugging logs or stack traces. Pasting error logs is a normal coding/debugging workflow.

Actual behavior

Codex can freeze after pasting certain logs, even in a new chat.

I am not sure what the root cause is or what the correct fix would be.