Ajaxy
Telegram A is not loading
Telegram Web page is not loading. It's just a blank white screen.
I had been using Telegram A for quite a while, but 2 days ago it just started to not load. I have to use Telegram K now :(
There's an error in console: DOMException: Failed to read large IndexedDB value
Could you please share the Application->Storage tab from the developer mode? This will help us resolve the issue more quickly.
Something strange happened. Telegram A is now loading (yay), but IndexedDB entries are almost gone. I remember trying to find, what record is so big that it can't be red and there were more entries than now. But here's tab, I hope it can somehow help you in finding cause of this issue.
Now I'm getting the same error "DataError: Failed to read large IndexedDB value"
I'm using Telegram K at the moment. (But I'd prefer to use A) (saying this in case K uses storage as well)
I am also having this problem now with https://web.telegram.org/a/ which I assume is what you guys mean by Telegram A.
I actually used the "Empty Cache and Hard Reload" option on chrome, so I am not sure if this changed the storage size, but it doesn't seem big right now:
But the error persists.
I found a workaround that I wanted to document here in case it's useful in solving the problem.
Unfortunately I am no longer in the broken state, so I'll describe from memory.
I started with inspecting the IndexedDB databases and I cleared the contents of all tables in four different account databases labeled to the effect of "account one", "account two". I also cleared the tables from a "common" account database. The problem still persisted with these changes.
I then simply dropped all of the databases and reloaded the page.
Telegram A now loads and brought me right to my messages, still logged in.
Now I only have one IndexedDB database tt-data and one table in that database store.
Hopefully this helps with either an app solution or helps someone looking for a workaround as I was this evening.
P.S. If I remember correctly, my storage summary in the chrome dev tools looked similar to the screenshots above.
Yes help me
Pada Jum, 25 Jul 2025 10.01, M Stefan Walker @.***> menulis:
mstefanwalker left a comment (Ajaxy/telegram-tt#380) https://github.com/Ajaxy/telegram-tt/issues/380#issuecomment-3116002348
I found a workaround that I wanted to document here in case it's useful in solving the problem.
Unfortunately I am no longer in the broken state, so I'll describe from memory.
I started with inspecting the IndexedDB databases and I cleared the contents of all tables in four different account databases labeled to the effect of "account one", "account two". I also cleared the tables from a "common" account database. The problem still persisted with these changes.
I then simply dropped all of the databases and reloaded the page.
Telegram A now loads and brought me right to my messages, still logged in.
Now I only have one IndexedDB database tt-data and one table in that database store.
Hopefully this helps with either an app solution or helps someone looking for a workaround as I was this evening.
— Reply to this email directly, view it on GitHub https://github.com/Ajaxy/telegram-tt/issues/380#issuecomment-3116002348, or unsubscribe https://github.com/notifications/unsubscribe-auth/BUUZNSEWTWHOUFEQ3JMKJR33KGFYDAVCNFSM6AAAAACA4MZQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJWGAYDEMZUHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Same here, even with an Indexed DB of only 23MB.
Solution was to open Dev Tools (F12 on Windows/Linux), then select the tt-data from IndexedDB, and click Delete database. Use it at your own risk!
