#Commands in GPT's backend container keep timing out

1 messages · Page 1 of 1 (latest)

shadow iglooBOT
#

Reported by @bright sentinel

Bug Report: Commands in GPT's backend container keep timing out
`Steps to Reproduce`

Ask GPT (web) to work on source code files. At some point it runs into backend timeouts in its container. This mostly concerns Python, but only because that's often used first. I also saw it while unzipping a <300 kb ZIP and also for other commands.

`Expected Result`

GPT's backend container commands shouldn't time out repeatedly.

`Actual Result`

Losing lots of time waiting for GPT to sort its container timeouts:

Command failed because it timed out.
Testing Python reading
Looks like there’s an issue with Python hanging when reading, but the initial part works. It might be due to an import issue. I’ll simplify this for testing, try running a basic Python read function, and see if that works more smoothly. Let's get this figured out!
Command failed because it timed out.

`Environment`

Windows 11, Edge

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

bright sentinel
#

I switched back and forth between ChatGPT 5.5 and 5.4 today and the timeouts only seem to happen in 5.5 where they happen a lot.

bright sentinel
#

Comparing 5.4 vs. 5.5 again today: No timeouts in 5.4, timeouts in 5.5 (especially Python). But: doing the same task 5.5 still finished faster and the results were better, despite having to handle its own backend tools' timeouts.

GPT-5.4 took 13m 13s, GPT-5.5 took 9m 28s. Both were tasked with improving DPI awareness of a settings window which previously used Windows' old bitmap resampling instead of proper font resizing. 5.4 failed in that it fixed the window to 100% scale, ignoring Windows' scale setting completely. 5.5 succeeded.

5.4 build only did the awareness/context side and top-level DPI message handling. It did not do the child-control/font/layout scaling work, which is why your Settings window stayed effectively unscaled.

Why 5.5 Settings looked better: it implemented actual control/font/layout scaling.
Why my Settings looked wrong: I only implemented awareness signaling, not the full layout/font side.

#

Imagine how much faster 5.5 could be without all the timeouts.

peak mural
#

if working with code for long periods than use codex :)