Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to restore session ("Failed to read large IndexedDB value") #27870

Open
Half-Shot opened this issue Jul 29, 2024 · 4 comments
Open

Unable to restore session ("Failed to read large IndexedDB value") #27870

Half-Shot opened this issue Jul 29, 2024 · 4 comments
Labels
A-Storage Storage layer of the app, including IndexedDB, local storage, etc. S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@Half-Shot
Copy link
Member

Steps to reproduce

  1. Boot up my machine from cold.
  2. Start element-web

Outcome

What did you expect?

Element Web starts normally and lets me use it.

What happened instead?

"Unable to restore session" error. Persistent even after restarting Element.

Operating system

Arch Linux

Application version

1.11.71-1

How did you install the app?

pacman

Homeserver

Synapse 1.105.1

Will you send logs?

Yes
@dosubot dosubot bot added A-Storage Storage layer of the app, including IndexedDB, local storage, etc. S-Critical Prevents work, causes data loss and/or has no workaround labels Jul 29, 2024
@t3chguy
Copy link
Member

t3chguy commented Jul 29, 2024

Duplicate of element-hq/element-desktop#1816

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Jul 29, 2024
@richvdh
Copy link
Member

richvdh commented Jul 29, 2024

Personally, I think "large IndexedDB value" is a different problem to the "invalid type" errors.

@Half-Shot: are you still seeing this? I'd love to spend some time digging into it with you.

@richvdh richvdh reopened this Jul 29, 2024
This was referenced Jul 29, 2024
Open
Closed
@Half-Shot
Copy link
Member Author

Half-Shot commented Jul 29, 2024 •
edited
Loading

@richvdh unfortunately I logged out and back in because I didn't think the broken session had any value :(. I can give you logs and eyewitness accounts?

@richvdh
Copy link
Member

richvdh commented Jul 30, 2024

ho hum. Thanks anyway!

@Half-Shot Half-Shot mentioned this issue Aug 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Storage Storage layer of the app, including IndexedDB, local storage, etc. S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@richvdh @Half-Shot @t3chguy