upgrading to v1.11.0 invalidates session

[3nprob]

Steps to reproduce

1. Have existing installation and signed in profile of electron-desktop v1.10.15.
2. Install v1.11.0
3. Start element-desktop

Outcome

What did you expect?

element-desktop starts and shows a signed-in view with rooms just as on v1.10.15.

What happened instead?

The following modal is displayed with a "Sign out" button being the only actionable:

Missing session data

Some session data, including encrypted message keys, is missing. Sign out and sign in to fix this, restoring keys from backup.

Your browser likely removed this data when running low on disk space. To help us prevent this in future, please send us logs.

Operating system

Linux (NixOS)

Application version

1.11.0

How did you install the app?

No response

Homeserver

No response

Will you send logs?

No

[3nprob]

Element may have been running during a period of high disk pressure but I assume the part about "your browser may have..." should only be applicable to element-web and not element-desktop?

If that assumption is not right then this issue may not be caused by the v1.11.0 upgrade.

[t3chguy]

@3nprob Element Desktop is built on Electron which uses Chromium under the hood, so a browser is still involved even if the phrasing isn't the clearest

[3nprob]

So would having disk pressure while Element Desktop is running explain why crypto keys were wiped? If so, is this documented anywhere and can anything be done about it? (I did try to look for chromium/electron references on such behavior but have not came up short)

[3nprob]

Potentially related issue: #18625

No flatpak here - running unsandboxed.

This happened simultaneously on two simultaneously running instances from the same installation of Element (separate profiles so should not be a cause of conflict there) but a third one on the same host, which was not running at the time that this got triggered, was unaffected.

I have no reason to believe that this occurred due do concurrently running processes attempted to modify the same file for both of these at the same time.

[turt2live]

this isn't a regression.

If your disk was nearly full then browsers, including desktop, tend to purge data we ask it to store, unhelpfully.

Considering a duplicate of one of these issues:

• Full indexedDB breaks element web #20931
• localStorage / IndexDB write failures are fatal #18423
• Desktop client loses keys when disk is full #4014
• QuotaExceededError on log database will bring up "Browser is missing features" #10891