I’ve been investigating the “Chat Memory Full” bug — here’s what I’ve found so far
I’ve been dealing with a strange ChatGPT problem for about a week, and after repeatedly testing it, checking the behavior across different conversations and devices, and looking through OpenAI’s status history, I think it’s worth documenting publicly.
Important: I am NOT claiming that I know the root cause. This is an investigation based on what I personally observed, what other users have reported, and what OpenAI has officially acknowledged.
The main problem
ChatGPT sometimes suddenly gives me an error along the lines of:
«“CHAT MEMORY FULL — TO CONTINUE UPGRADE OR START A NEW CONVERSATION WITH THE SUMMARY OF THE WHOLE LAST CONVERSATION”»
The weird part is that this does not behave like a normal long-conversation limit.
I’ve seen it happen in different conversations, including conversations that aren’t particularly large. Creating a new conversation and continuing from a summary can also eventually lead to the same problem again, sometimes after only around 10–20 messages.
That is what initially made me suspicious.
I tested the obvious explanations
I’ve tried the normal troubleshooting steps:
- Closing and reopening the Android app
- Signing out and signing back in
- Completely uninstalling and reinstalling the Android app
- Testing different conversations
- Creating new conversations
- Testing on the ChatGPT website
- Previously deleting some saved memories
The problem continued.
Most importantly, it happens on both Android and the web with the same account.
There is also no storage-full indicator in my Memory settings.
So I’m having trouble explaining the behavior as simply “your saved Memory is full.”
It isn’t limited to one conversation
Two particularly affected areas for me are:
1. A long-running AU/story conversation
This conversation became extremely difficult to continue.
2. Conversations I created specifically to investigate this exact bug
This is probably the strangest part.
Some of the conversations created specifically to investigate the “Chat Memory Full” problem eventually developed similar behavior themselves.
That makes it difficult to explain as a problem with one corrupted conversation.
There’s also an Android-only UI/TTS weirdness
While investigating the problem, I found another strange behavior involving the Android app’s UI and text-to-speech controls.
By switching between conversations at very specific moments, the interface can briefly behave differently and expose UI controls that normally aren’t available in that state.
I’m deliberately not presenting this as proof of the cause because I don’t know what causes it. I’m documenting it because it was reproducible enough for me to notice a pattern.
This particular behavior appears to be app/UI-specific, rather than something I see in the web interface.
And then there are the other failures
Around the same period, I’ve also encountered or seen reports of:
- Responses getting stuck thinking indefinitely
- Conversations failing to respond
- Conversations becoming inaccessible or behaving strangely
- Image-related problems
- Other UI inconsistencies
- Problems affecting multiple conversations rather than one specific thread
At first I thought I might simply be unlucky.
After seeing similar reports from other users, I stopped thinking that was a reasonable explanation.
I am apparently not the chosen victim of the gods. 
OpenAI’s status history is interesting
This is where things get more interesting.
OpenAI’s own status history shows several incidents around this period.
On September 29, 2026, OpenAI reported elevated errors across ChatGPT, Codex and the API, affecting a very large number of components. The listed affected ChatGPT components included conversations, login, Work, search, file uploads, Voice, GPTs, Image Generation, Deep Research, Agents, Sites and connectors/apps.
OpenAI eventually marked that incident resolved and said a detailed Root Cause Analysis (RCA) would be published.
Then on October 6, OpenAI separately reported elevated errors affecting ChatGPT conversations.
So there definitely have been broader reliability problems around the same period I’m experiencing this.
That does NOT prove that those incidents caused my “Chat Memory Full” problem.
But it makes the possibility of a broader backend/account/conversation-state problem more interesting.
My current hypothesis is
«There may be a conversation/account-state/UI/backend problem causing ChatGPT to incorrectly treat certain conversations as unable to continue, potentially alongside other reliability problems that have occurred recently.»
It could ultimately turn out to be something completely different.
That’s why I’m documenting the observations rather than declaring a root cause.
What makes this particularly strange
The biggest thing I can’t reconcile is:
If this were simply saved-memory capacity, why does the behavior repeatedly appear across different conversations, including new ones, and why does it also occur on the web?
And why does creating a new conversation sometimes only postpone the problem rather than actually fixing it?
That’s the part I’d like other users to compare against.
If you’ve experienced something similar, I’d be interested in hearing:
- What platform were you using? Android / iOS / web / desktop?
- Did it happen in an old conversation or a new one?
- Did creating a new conversation actually fix it?
- Did it happen again after continuing the new conversation?
- Did your Memory settings show that storage was actually full?
- Did you experience responses getting stuck on “Thinking…” indefinitely?
- Did reinstalling the app or signing out/in change anything?
Again, I’m not claiming to have solved this.
I’m trying to collect enough observations to determine whether this is one bug, several unrelated bugs, or different symptoms of a larger reliability problem.
If anyone else has experienced this, please share your observations. The more reproducible the pattern is, the easier it should be to figure out what is actually happening.
If u feel like that the rant about is AI then u are correct WELL I was investigating this with ChatGPT while changing chat whenever they got also got the same problem Soo when I told got that I am going to make a post it gave me this and me being lazy just copy pasted BUT the problem is real and should be recognized by OpenAI also this started to happen to me around 30 September 2026