Full indexedDB breaks element web

[Yoric]

Steps to reproduce

I first noticed this in a fosdem room, but this sems to be generalized across rooms. I cannot send messages at all, afaict.

chat.element.io works, though

Outcome

Cannot send messages. Messages show as "Failed to send".

Operating system

Ubuntu

Browser information

Firefox 96.0 (64-bit)

URL for webapp

develop.element.io

Application version

Element version: 64242a0-react-7f3f18604417-js-2d23330b74da Olm version: 3.2.8

Homeserver

matrix.org

Will you send logs?

Yes

[Yoric]

Ah, I find in the logs

Uncaught (in promise) DOMException: The quota has been exceeded.

So I guess it's a matter of localStorage/indexedDB being full. We should find a way to fix this.

[Yoric]

I've removed my indexedDB manually. Unfortunately, Element Web won't launch at all now.

Uncaught (in promise) Error: No connected database
    flushPromise rageshake.ts:246
    flush rageshake.ts:243
    flush rageshake.ts:509
    initRageshake rageshakesetup.ts:45

[aaronraimist]

Duplicate of #18423. Related: #7465 #13290 #12131 #12625

To get back in maybe going to the Lock icon in the URL bar and clicking Clear cookies and site data will help.

[Yoric]

Ok, restarting Firefox after removing indexedDB seems to have done the trick.
However, my Element Web self-destructed again 10 minutes before my Fosdem talk. Not ideal.

[Yoric]

Duplicate of #18423

To get back in maybe going to the Lock icon in the URL bar and clicking Clear cookies and site data will help.

I can do that. Random user can't.

[aaronraimist]

Which is why #18423 is open

[aaronraimist]

However, my Element Web self-destructed again 10 minutes before my Fosdem talk. Not ideal.

Delete some stuff from your disk so you have some free space

[Yoric]

Note that I have 300Gb available on my hd, so that's not the issue.

[Yoric]

As suggested by @novocaine , this issue should NOT be closed as dup to #18423 as the hard drive was NOT full.

[novocaine]

Yikes, apologies I might have been unclear - if its a result of the browser allocated disk space filling up, then I think that is part of #18423 .

I'm not sure I quite trust the quota message though - are you able to check the size of your IndexDB ?

[Yoric]

I'm not sure I quite trust the quota message though - are you able to check the size of your IndexDB ?

Not a few days after cleaning it up, I'm afraid.

[jlemangarin]

I confirm this issue happens with a lot of disk space available and with no information in the client, just the message not sending.

It happens with actually not a lot of tabs opened (like 5) and with a decent amount of rooms (~100). I'm concerned about this hard limitation in IndexDB also, do you know about any issue opened outside of Element ?

Also maybe Element should clear some space when it's reaching the limit, even if it has to download again some resources later.

I also confirm that this modification (#18423 (comment)) in Firefox resolves the issue but that's not something a end user can do.

[turt2live]

Mine managed to break in such a way where I got notifications but not messages in the timeline. No obvious errors presented to me as a user that would suggest anything was wrong (not even a "disconnected from homeserver" warning)

[richvdh]

I'm not really clear how this is different from #18423 - can anyone clarify? Otherwise suggest we close this once more.

[t3chguy]

Closing in favour of #18423