openai / openai/codex

[Windows] /feedback upload repeatedly fails and causes severe system slowdown

Open
#38,130 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug connectivity performance windows-os
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

Title: [Windows] /feedback upload repeatedly fails and causes severe system slowdown

I encountered a scheduled Automation failure in the ChatGPT/Codex desktop app and attempted to report it using /feedback.

The feedback upload repeatedly failed.

Environment:

  • OS: Windows
  • App: ChatGPT/Codex desktop app
  • App version: Unknown
  • Date: 2026-08-12 KST

Observed behavior:

  1. I opened /feedback from the existing Codex conversation containing the diagnostic report.
  2. The first three upload attempts failed.
  3. During those attempts, the entire computer became severely unresponsive and the mouse cursor barely moved.
  4. The desktop app also terminated unexpectedly during an earlier attempt.
  5. I restarted both the app and the computer, but the problem continued.
  6. I then disabled “Include all browser tabs and browser logs” and tried again.
  7. The upload still failed with “Feedback upload failed.”
  8. The displayed feedback/session ID remained unchanged.

Expected behavior:

  • The feedback should upload successfully.
  • Collecting or uploading diagnostic information should not make the computer unresponsive or crash the app.

Underlying issue I was attempting to report:

  • An ACTIVE weekday Automation scheduled for 2026-08-12 08:40 KST did not create a heartbeat Submission.
  • The same Automation ran successfully the previous day.
  • A separate Automation test succeeded later that day at 12:49:57 KST.
  • A detailed diagnostic report is available.
  • The relevant session/thread identifier is being kept privately and can be provided to an OpenAI team member if requested through an appropriate channel.

Attachments:

  • Screenshot of the feedback upload failure
  • Screenshot of the unexpected app termination

Sensitive identifiers have been removed from the public screenshots.

Image Image

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.

Research direction

Start by reproducing the /feedback upload failure on Windows, testing both with and without browser tabs and browser logs included. Observe whether repeated attempts cause system unresponsiveness or app termination; done means diagnostic feedback uploads successfully without severe slowdown or a crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.